if you consider that in Devonian period (375 million years ago) days were about 22 hours long and the year had 400 days (Since the length of a day increases by 0.002 seconds per century).
The rate of slowing down is actually decreasing as moon moves away from Earth ( 4 cm per year ).
Re:Duh ! ... It's an exe + bootstrap for JIT
on
A .Net CPU
·
· Score: 1
I never say that JITer suck, just is difficult to write one. MS and Mono they have pretty good JITers.
The "Why?" part is obvious
1) Makes compilers for.NET easier to write
2) Makes dynamic code (code on the fly) easier to write
That means that the difficult things are concentrated in one service (or component) and not spread to all tools and applications
Re:Duh ! ... It's an exe + bootstrap for JIT
on
A .Net CPU
·
· Score: 1
Yes, that's correct with a minor detail
.NET can be pre-JITed (converted to machine code once and use that image at runtime) That will eliminate the JIT stage, but is a practice that is rarely applied, because you will lose all optimizations that JITer does at runtime.
Re:Duh ! ... It's an exe + bootstrap for JIT
on
A .Net CPU
·
· Score: 1
1) the.exe bootstraper is never executed in Windows server 2003 which recognizes.net apps natively
2)What the paper demonstrates is a small switch/case with few if (.net) vs a big switch/case (jvm), how can that be hoops it's beyond me
Re:.Not a .NET CPU
on
A .Net CPU
·
· Score: 2, Interesting
Polymorphic translates : easier to write compilers, harder to JIT it.
Direct CPU mapping has the same difficulty as JVM bytecode, polymorphic instruction set is not a problem compared with the dynamic loading types, inlining, virtual calls, GC etc that the CPU architecture must solve
Tamir Khason has another list that also predicts the success of a language based on author's photo
Re:Java is not only a language
on
Java 1.5 vs C#
·
· Score: 1
Java the platform doesnot have generics, doesnot enforce checked exceptions, has not autoboxing etc.
They are all enabled by the java "compiler" and not by the Java "the platform" or "the system"
Sorry but the only reason i rejected Java some years ago was checked exceptions.
IMHO that was a major design fault of the Java designers to abuse the structured exception mechanism to provide semi-cooked validation of contracts. That alone turned every simple operation in Java to a try/catch block
Java's implementation of generics is just a compiler hack, the underlying byte code has not changed. The only benefits are some compiler errors and warnings and not performance and storage effiency that.net 2.0 will offer.
I cannot understand how a free GUI, can become a standard on win32 when Windows next version are converting to Avalon (winfx) abandoning win32 and when is based on C++ RTTI (only C++ can take advantage of it) when Windows present and future is.NET and C#.
if it's "bulk of the work" and requires "low skills" as you say, then a beowulf cluster of developers will help. The mythical man month, does not have a place in such a case.
You seem to over-estimate MS
Just few years ago, in MSDN was an article about how bad implementation inheritance was and how good COM interfaces solve everything. MS.NET is an unfinished project (IMHO still in BETA, even if MS has name those BETA versions as 1.0 and 1.1), that few inside MS understand. You can verify this by watching the MS newsgroups, where the majority of MS employees there are just newbies. But it seems Miguel does not get it, even if mono currently supports features that.NET 2.0 will have, he is still behind a Windows.Forms implementation which in 2 years will become obsolete.
I wish mono could follow it's own way (a XUL/XAML combination for example), providing a mono-only x-platform GUI and ignoring any compatibility with the awfull Windows.Forms. Most of the code is out there and OS, is just a decision and the first versions can be delivered before Avalon.
Name a project that has done more damage in OS than Linux.
to give you some numbers
Windows 91% share, 1 GUI, 1 Shell, some thousand developers support it
OSX 3% share, 1 GUI, 1 Shell,less than a thousand developers support it
Linux 1% share, 134 GUI, 15 Shell and millions of developers support them
Slashdot Mirror
Malicious Software Removal Tool ?
How is that different than any antivirus, with just 10 virus signatures ?
It is just unbelielivable, what marketing dep of MS can think, to hide the facts and sell crap
if you consider that in Devonian period (375 million years ago) days were about 22 hours long and the year had 400 days (Since the length of a day increases by 0.002 seconds per century).
The rate of slowing down is actually decreasing as moon moves away from Earth ( 4 cm per year ).
I never say that JITer suck, just is difficult to write one. MS and Mono they have pretty good JITers.
.NET easier to write
The "Why?" part is obvious
1) Makes compilers for
2) Makes dynamic code (code on the fly) easier to write
That means that the difficult things are concentrated in one service (or component) and not spread to all tools and applications
Yes, that's correct with a minor detail
.NET can be pre-JITed (converted to machine code once and use that image at runtime)
That will eliminate the JIT stage, but is a practice that is rarely applied, because you will lose all optimizations that JITer does at runtime.
1) the .exe bootstraper is never executed in Windows server 2003 which recognizes .net apps natively
2)What the paper demonstrates is a small switch/case with few if (.net)
vs a big switch/case (jvm), how can that be hoops it's beyond me
Polymorphic translates : easier to write compilers, harder to JIT it.
Direct CPU mapping has the same difficulty as JVM bytecode, polymorphic instruction set is not a problem compared with the dynamic loading types, inlining, virtual calls, GC etc that the CPU architecture must solve
Tamir Khason has another list that also predicts the success of a language based on author's photo
Java the platform doesnot have generics, doesnot enforce checked exceptions, has not autoboxing etc.
They are all enabled by the java "compiler" and not by the Java "the platform" or "the system"
Sorry but the only reason i rejected Java some years ago was checked exceptions.
IMHO that was a major design fault of the Java designers to abuse the structured exception mechanism to provide semi-cooked validation of contracts.
That alone turned every simple operation in Java to a try/catch block
Java's implementation of generics is just a compiler hack, the underlying byte code has not changed. The only benefits are some compiler errors and warnings and not performance and storage effiency that .net 2.0 will offer.
I cannot understand how a free GUI, can become a standard on win32 when Windows next version are converting to Avalon (winfx) abandoning win32 and when is based on C++ RTTI (only C++ can take advantage of it) when Windows present and future is .NET and C#.
if it's "bulk of the work" and requires "low skills" as you say, then a beowulf cluster of developers will help. The mythical man month, does not have a place in such a case.
You seem to over-estimate MS .NET is an unfinished project (IMHO still in BETA, even if MS has name those BETA versions as 1.0 and 1.1), that few inside MS understand. .NET 2.0 will have, he is still behind a Windows.Forms implementation which in 2 years will become obsolete.
Just few years ago, in MSDN was an article about how bad implementation inheritance was and how good COM interfaces solve everything.
MS
You can verify this by watching the MS newsgroups, where the majority of MS employees there are just newbies.
But it seems Miguel does not get it, even if mono currently supports features that
I wish mono could follow it's own way (a XUL/XAML combination for example), providing a mono-only x-platform GUI and ignoring any compatibility with the awfull Windows.Forms. Most of the code is out there and OS, is just a decision and the first versions can be delivered before Avalon.
Point to me a succesfull OS project that has just "idea people"
OS in full of ideas, but lacks strong managers to give solid directions.
Name a project that has done more damage in OS than Linux.
to give you some numbers
Windows 91% share, 1 GUI, 1 Shell, some thousand developers support it
OSX 3% share, 1 GUI, 1 Shell,less than a thousand developers support it
Linux 1% share, 134 GUI, 15 Shell and millions of developers support them