| |||||||||||||
Java FailJava FailPosted Mar 28, 2011 15:40 UTC (Mon) by ncm (subscriber, #165)In reply to: GCC 4.6.0 released by HelloWorld Parent article: GCC 4.6.0 released
Correct as far as it goes... Java's designers demonstrated again and again that they didn't even understand the C++ of 1992 that they copied Java from. The litany of "boneheaded mistakes" just goes on and on: 16-bit characters. Default virtual. No destructors. Garbage collection. Ugly NamingConVention. Threading model unimplementable on modern multi-CPU designs. Enforcedly slow execution model. I could go on.
C# is even worse, because it shares almost all the mistakes of Java, and adds new ones despite full benefit of hindsight.
Go's designers had even more hindsight to work from, so each such mistake counts more. They got some doozies. However, it is marginally more interesting than D.
(Log in to post comments)
Java Fail Posted Mar 28, 2011 17:16 UTC (Mon) by nteon (subscriber, #53899) [Link]
is there a 'modern' language you _would_ recommend?
Java Fail Posted Mar 31, 2011 18:08 UTC (Thu) by ncm (subscriber, #165) [Link]
There is still no plausible successor to C++, as much as we might like one.
Any such successor can only be produced by someone who understands it, and why it has been successful despite all the historical baggage it must drag along. It would be at least as expressive, but 90% smaller. Unfortunately most efforts sabotage themselves at the outset by including garbage collection and CONS or its equivalent. A powerful-enough language should be able to express those in the library, and not need them built into the core. Likewise, control structures, inheritance, and maybe even function argument lists.
|
|||||||||||||