About 2 years ago, someone told me that in order to do my job, I would have to program in java for the web, but, not to worry, it too was an object oriented language and the transition from C++ would be a breeze. What they didn't say is that to get anything done in web java, you have to learn at a minimum 5 concepts; java, JSP, XML, HTML, ant. And that does not include the servers such as Tomcat, WebLogic, Sun One, etc, or the myriads of IDE that popup every 6 months or so. Furthermore, we still don't have struts involved here, nor EJB or even all the requirements of manifest files, classpath, intricacies of JVM class loader, class visibility, parameter files, and the virtually hundred of support packages that have become standards of some sort.
And to top it all, someone had the cruel idea of pretending that javadoc would be the ultimate, final, decisive repository for all the documentation necessary to use a class in a package. Of course, interdependencies and prerequisites are too much to hope for. Example are a no-no since java is so self explanatory anyway.
So, maybe some of you have decided to become elephant hunters. Well, for some of us, the enterprise decided that everyone would be eating whale, and they made sure there would be plenty around for everyone. So, while you talk about new standards and improved ways of doing thing, all I see is new poorly documented package making their way to my desktop and my work environment with a mail message that they are now the "standard du jour" which we will use from now on.
Please, just stop it! Take a break. Go on vacation for 2 years. Put a freeze on code change. Let us finish the first whale before you give us another one.
Sincerely,
Fed Up.
|
java.net RSS Feeds
