| > The garbage collector is terrible But the section talks about immutable strings (nothing to do with GC),
syscalls (ditto), and only at the end about no manual memory allocation. Not
even a word about why GC in Java is terrible (and why automatic memory
management in Ruby and Python is not terrible). > No pointers Why is it a bad thing? Only because author wants to do pointer arithmetic? > No preprocessor And good for Java. CPP is vastly underpowered, thus being quite a trouble.
Either macro system should be powerful, working on AST, or not there at all. > No UNIX Syscalls Oh, my. No UNIX syscalls in web browser. No syscalls on a DVD player. What
a shame. > It’s not suitable for big projects ElasticSearch and Hadoop beg to disagree. I wonder how big systems has the
author in his portfolio. > It’s not good as a PoC language Because...? Only because it's verbose? We've been through this few arguments
before. > No global variables Author fails to provide any argument why this is bad. "I use them for
debugging" is very, very, very weak. > Java browser applet are insecure So don't use them. Implementations of applets suck, we all know it, but nobody
uses those anymore for anything serious (except for hardware vendors, who are
generally clueless with regard to writing software). I don't see why should people abandon Java for writing services because
applets suck. > Why then there are non-free implementations? What’s wrong with OpenJDK? What is IcedTea? Which implementation belongs to Sun? One could say pretty much the same about Ruby, Python or C. I don't see why
should this be held against Java and not against C. Most of the arguments are pure trash. Don't bother reading. |