J2EE was designed to do big jobs with proprietary tools. Who in their right mind would want to code an EJB by hand when their are alternatives such as Hibernate.
Also, LAMP tends to scale, not because it was designed to but because it is simple. For instance, you can learn the state-diagram for the creation/deletion of a stateful session bean, or you can just use a browser cookie 90% of the time.
Personally I prefer to code in Java, but I have to admit that I am much more productive in Perl and the like.
KDE definately has it's act together better than GNOME, but I still tend to use GNOME. For various reasons, projects outside the KDE/Gnome communities prefer to support Gnome in preference to KDE. For instance Mozilla, OpenOffice, Java SWT.
Slashdot Mirror
How are they going to enforce this if I start buying from outside the U.S. ?
J2EE was designed to do big jobs with proprietary tools. Who in their right mind would want to code an EJB by hand when their are alternatives such as Hibernate.
Also, LAMP tends to scale, not because it was designed to but because it is simple. For instance, you can learn the state-diagram for the creation/deletion of a stateful session bean, or you can just use a browser cookie 90% of the time.
Personally I prefer to code in Java, but I have to admit that I am much more productive in Perl and the like.
KDE definately has it's act together better than GNOME, but I still tend to use GNOME. For various reasons, projects outside the KDE/Gnome communities prefer to support Gnome in preference to KDE. For instance Mozilla, OpenOffice, Java SWT.
I will vouch for this anonymous coward and hopefully raise the score of his post.