Well begun!

Though some have been grumbling right from its launch I think the new initiative of a community place is a welcome step. Moreover, I think the fact that it is “blessed by SUN” will add to the likelihood of it becoming the “new central meeting place”. Now, I don’t wish to undermine the feeling here that the other existing communities should not be ignored in the effort. However, its still early days to comment on its outcome.

And I am very optimistic on all this development. As Sun Director Ingrid Hoogen told  Sue Spielman:

The Developer community needs to feel cool again. It’s time to get excited and bring the energy level back up and the infusion back in the community.

I am also looking forward to the new tool, code-named Project Rave, which is intended to make writing enterprise Java applications  easier for developers using the JavaServer Faces technology.

Another new site has a catchy look and rightly intended to “appeal to the masses” and attract them to the stronghold. The new Java logo looks pretty nice too. This, together with the “Java Powered” branding campaign may or may not surface as the heralding of a new era but it certainly is a new chapter in Java. A chapter well begun.


Will Tiger be scary?

I was very happy when I wrote this but Matt Quail scared me badly. Though pertinent, I hope such scepticism is later proven unfounded. Don Park insists that there was no need to go for features like “Generics” when there were other critical pending issues like extending SWT and incremental installation. But as Joshua Bloch said, none of the changes will be that hard for developers to adjust to…one that might require some adjustment, it would be generics, because you’ll have to get used to providing additional information in declarations. Instead of merely saying:

List words = new ArrayList();

You’ll have to say:

List<String> words = new ArrayList<String>();

Moreover, many features have been due for long. For instance, using constant interfaces has been a prevalent and sometimes recommended practice despite of us knowing that Interfaces should only be used to define types; any other use is an abuse. Using an interface causes internal details — such as constants — to leak into the class’ public API. I am no expert but methinks static import was a much needed feature.


Sun: Empathising with Programmers?

Sun Microsystems
Sun Microsystems (Photo credit: Wikipedia)

My tête-à-tête with EJB was not pleasant. Though involved in server-side development I have never been into developing full-fledged J2EE applications using EJB. Despite of joining a crash course it scares me. Many fellow Java developers would perhaps agree: conceptually, EJB seems intimidating. It seems Sun Microsystems has now awoken to the fact as well.

Sun’s efforts to augment the number of Java developers from the existing 3 million today to 10 million will emphasize on “easier development”. Rich Green, vice president of tools at Sun says:

“..we’ll focus on enhancements to the Java platform that cater to simpler development paradigms..Ease of development is a theme at all levels, not just tools, but APIs, platform definitions, etc. are all trending to support this notion in a more focused sense…you would agree that there (are) millions of folks out there who are not necessarily creating J2EE-scalable applications. They’re creating lightweight applications. That’s a group of individuals that have been slower to come to the Java platform than others…”

Better late than never!