Comments on: Tell us why your language sucks http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/ Wed, 10 Feb 2010 18:19:37 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: david http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/comment-page-1/#comment-1067 david Thu, 21 Jan 2010 12:27:44 +0000 http://www.drmaciver.com/wordpress/?p=85#comment-1067 Absolutely, but sometimes the specific complaints are interesting. :-) Absolutely, but sometimes the specific complaints are interesting. :-)

]]> By: M.S. Babaei http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/comment-page-1/#comment-1065 M.S. Babaei Thu, 21 Jan 2010 01:33:23 +0000 http://www.drmaciver.com/wordpress/?p=85#comment-1065 "There are only two kinds of languages: the ones people complain about and the ones nobody uses" --Bjarne Stroustrup http://www2.research.att.com/~bs/bs_faq.html#really-say-that “There are only two kinds of languages: the ones people complain about and the ones nobody uses” –Bjarne Stroustrup

http://www2.research.att.com/~bs/bs_faq.html#really-say-that

]]> By: bgsu_drew http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/comment-page-1/#comment-1062 bgsu_drew Sat, 09 Jan 2010 02:29:29 +0000 http://www.drmaciver.com/wordpress/?p=85#comment-1062 Java: * Too low level - try doing common tasks such as converting a file to a string or validating XML against a schema. Java is definitely not meant for scripting. * Tools are maddeningly slow, like try redeploying to an IBM Websphere server. * Constantly changing enterprise standards that make it feel like you are trying to hit a moving target... and none of which ever seem to get the API quite right. Is EJB3 great? I dunno, cause my company is stuck using EJB2 on WAS6.1 on J2EE v1.4. * Java code is not elegant or fun. Yeah, it's subjective, but there's no closures (Predicates don't count) and no literal collection initialization. * Many frameworks required to do anything useful and high barrier to entry. Front End (Struts) + Data Persistence (Hibernate) + Wire it all together (Spring) + Build System (Maven) + App Server (Glassfish). This is exactly why Rails and Grails so attractive to web developers. Java:
* Too low level – try doing common tasks such as converting a file to a string or validating XML against a schema. Java is definitely not meant for scripting.
* Tools are maddeningly slow, like try redeploying to an IBM Websphere server.
* Constantly changing enterprise standards that make it feel like you are trying to hit a moving target… and none of which ever seem to get the API quite right. Is EJB3 great? I dunno, cause my company is stuck using EJB2 on WAS6.1 on J2EE v1.4.
* Java code is not elegant or fun. Yeah, it’s subjective, but there’s no closures (Predicates don’t count) and no literal collection initialization.
* Many frameworks required to do anything useful and high barrier to entry. Front End (Struts) + Data Persistence (Hibernate) + Wire it all together (Spring) + Build System (Maven) + App Server (Glassfish). This is exactly why Rails and Grails so attractive to web developers.

]]> By: brazzy http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/comment-page-1/#comment-1061 brazzy Tue, 05 Jan 2010 16:55:10 +0000 http://www.drmaciver.com/wordpress/?p=85#comment-1061 Java: Most of the problems boil down to one thing, which is also responsible for a good part of Java's success: Sun's obsession with downwards compatibility. - It makes adding language features agonizingly slow and often leads to ugly compromises (such as generics based on type erasure) - It leaves the API library cluttered with warts and remnants of design errors, many of them left from the days of Java 1.0 Java:

Most of the problems boil down to one thing, which is also responsible for a good part of Java’s success: Sun’s obsession with downwards compatibility.

- It makes adding language features agonizingly slow and often leads to ugly compromises (such as generics based on type erasure)
- It leaves the API library cluttered with warts and remnants of design errors, many of them left from the days of Java 1.0

]]> By: odrzut http://www.drmaciver.com/2008/02/tell-us-why-your-language-sucks/comment-page-1/#comment-1060 odrzut Tue, 05 Jan 2010 16:36:33 +0000 http://www.drmaciver.com/wordpress/?p=85#comment-1060 Clojure - error messages are horrible, using/requiring/importing libraries is more convulted than it could be, to run clojure program you have to specify classpath with all classes it uses Clojure – error messages are horrible,
using/requiring/importing libraries is more convulted than it could be,
to run clojure program you have to specify classpath with all classes it uses

]]>