Gosling on OS Java
"If we do something to make Java even more open-source than it is already, having safeguards to protect the developer community will be something we pay a lot of attention to."
In today's Weblogs , James Gosling blogs about Open sourcing Java . He addresses IBM's open letters and their history of contributing to Java. One interesting point is the Swing/SWT/AWT issue. Gosling notes that "IBM was the major mover that led to the creation of the Swing API to replace the AWT api. They contributed many engineers to the Swing team. Viewing that time in hindsight, it is more than slightly ironic that these days they're endorsing SWT, which is essentially a clone of the AWT architecture, which they had strongly condemmed back when the decision to create Swing was being debated."
Every time we have had a conversation about open sourcing Java here on java.net, the feedback has been fairly balanced. There are folks on both sides of the open source issue for whom it is a religious matter. There are others who express their concerns with IBM and others about what could happen to the platform. Gosling summarizes these folks as being "afraid that if Java is open-sourced then someone will try to fragment the community by creating incompatible versions of Java and ignore the community process, just like Microsoft did. Microsoft did a lot of damage to the community and many developers strongly do not want that to happen again." As the quote at the top shows, this is front and center in Sun's mind.
Users who sign up for one flavor of instant messaging still want to be able to chat with friends who have signed up with another. In Anti-Social Software Brendon J. Wilson notes that "
Social networking systems have followed a similar path, coding users into the very same corner[...] Social networking systems are pathologically anti-social on three fronts: their lack of functionality, lack of a web services API, and lack of federation."
Rory Winston questions whether insulating developers from the dataebase layer is always a good idea in O/R Mapping and Performance. He presents three instances of performance impact that developers should be aware of: Improperly configured or non-existant lazy initialization, the inability to use database-specific optimizations, and cache configuration.
Bob Lee posts on the "Default" JDK in IDEA. He tells you how he worked around different JDK names on two different installations.
Also in Java Today, JSR 175 introduces metadata to the Java programming language. In "Declarative
Programming in Java" Narayanan Jayaratchagan says that "Every new release of Java has introduced new features, but few warrant a new way of thinking to realize their full potential. Using annotations effectively to simplify programming in Java requires a shift in our thought processes. Even though we use declarative programming languages such as SQL and XSLT most frequently, it may take some time for us to understand how to use declarative and imperative
Vikram Goyal moderates the first discussion in our new forum The Programming Profession. He kicks off tips to technical interviewing with an article titled So you don't know what a static inner class is? Think back to your experiences on either side of the interview process and chime in.
Is Brooks' definition of architecture really just another way of talking about end-user usability / interaction design? What about the interface between the different facets and components of the system?"
Is there a mismatch between what your developers can do and what you are asking them to do? rickcarson suggests that the problem may not be one of available skills. In Bargain Developers he writes "about a kid in the US who was failing maths. But when they asked him about baseball, he could rattle off all sorts of university level statistics about it... and the kid is like 8 or 10 yrs old. He's not stupid, its just that he finds maths boring, and baseball interesting". His moral is that "If you want to change the low productivity programmers into high productivity, find what they like and are good at, and get them doing that".
In today's Projects and Communities , the Java Desktop community tip of the week features a site that "points to a bunch of nice web tools for choosing color schemes. [O]ne even shows you how the colors look to people with various kinds of color blindness! "
The JavaOne Wiki page is intended as a way to let people know about java.net community members who are doing presentations at JavaOne. Add your talks and create pages to arrange meetings while at the conference.
In today's java.net News Headlines
- Jikes 1.2
- Geronimo 1.0 Milestone Build M1
- Eclipse Web Tools Platform Project
- Sun Should Make Java a True Open Standard, IBM Repeats
- Opinion: Why Sun Should Just Close Shop
- Employees Prefer Personal Net Time to Morning Coffee
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 by news director
Steve Mallet before being posted to the site. You can also subscribe to
News RSS feed.
Current and upcoming
- April 30 - May 2 Twin Cities Software Symposium
- May 6-8 The ServerSide Java Symposium
- May 8 Kwarup do DFJUG
- May 10-14 JAX 2004
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. All java.net members can subscribe to the email
updates for the site at the href="https://java-net.dev.java.net/servlets/ProjectMailingListList">
java-net Mailing Lists page. You must be logged in to subscribe
to the javanet_Daily and javanet_Weekly lists. 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.