Perl vs. Java
All about trust
There has been great feedback to my whining this week about the OS community treatment of Java. Really, I'm not complaining so much as I'm trying to understand the issues. I am hoping that since these blogs also scroll on the O'Reilly network pages, someone from the Perl community (chromatic?) can help me understand this. The following is a question and not a troll - really.
So yesterday I was in a meeting hosted by a company that is preparing to open source a major project (no - it was not a meeting with Sun about Java - don't start the rumor mill). A prominent voice from the community made the observation that Perl development filters through Larry and that he has a lot of control on the process. In fact, at his State of the Onion, Larry talked about a horrible year of dealing with a stomach tumor and complications that arose. Of course our concerns are first with his health, but even he thought a bit about what impact that had on Perl.
How does Sun's control of Java and the mechanisms that Sun has set up for introducing new features into Java compare to Larry's control of Perl and the mechanisms for introducing new features there?
In Also in Java Today , the way you print in a Java application has changed in almost every release of J2SE. In Printing Components with PrinterJob "you will use PrinterJob to print a GUI component. Because components are what make up the UI of your application, this is how you can enable a user to print exactly what they see on the screen. You will be able to set attributes and specify PageFormat options for printing."
Steve Holzner's "Eclipse Cookbook" offers recipes for hundreds of Eclipse issues. In this week's excerpt from ONJava.com, Steve looks at customizing an existing perspective to create just the right combination of views for you. In a second recipe, he shows how to speed up Eclipse by turning off syntax and problem-checking features if you don't need them.
John Reynolds makes a Public plea to the EJB 3.0 expert group: Please review the EJB 2.0 CMP and JDO FAQ in today's
Steve Mallet posts video on Open Source Java Proposed.
Back to getters and setters in today's
Forums. Marc writes " In almost the places I've seen getters/setters, it is to expose a property that should be public. Some people say that properties should not be exposed, but I've never heard a convincing argument for this."
Who should Check parameters for validity? Coxcu writes "This is best done by the compiler. Failing that, there should be tools to help the programmer do it."
Robilad wants to know why "all the nice specifications drafts from JSRs using the JCP 2.6 process come with a nice catch: you are not allowed to discuss them with anyone who hasn't licensed the specifications. Interestingly, the final releases do not have such a clause. What is the reasoning behind that?
In today's java.net News Headlines
- Beehive Comes Alive
- ApacheCon Call For Papers Deadline Now Aug 2nd
- JaxMEXS 0.3
- Spring Framework 1.1 RC1
- J2ME Polish 1.0
- Drools 2.0 beta17
- IzPack 3.6.0
Registered users can submit news items for the
href="http://today.java.net/today/news/">java.net News Page using
our news submission
form. All submissions go through an editorial review before being posted to the site. You can also subscribe to
News RSS feed.
Current and upcoming
Registered users can submit event listings for the
href="http://www.java.net/events">java.net Events Page using our
href="http://today.java.net/cs/user/create/e"> events submission
form. All submissions go through an editorial review before being
posted to the site.
Archives and Subscriptions: This blog is delivered weekdays as the
Today RSS feed. Also, once this page
is no longer featured as the front page of
java.net it will be archived along with other past issues in the href="http://today.java.net/today/archive/">java.net Archive.