Twitter Updates 2.2.1: FeedWitter

Saturday, January 19, 2008

Changes have to happen in JavaME area

I read a VERY GOOD BLOG called Possibly the last MIDP specification, you will ever review. The writer Gorkem Ercan gave us the information that the public review for the JSR 271(MIDP 3 ) has started and what he thought about the future for Java in mobile devices.

I totally agree with Gorkem Ercan about that we in the mobility area have some problems with the JCP process, as it works today.

Sorry, I don't get excited about that JSR 271, (MIDP 3) is now in public review or that JSR 232 has published (some days ago) an updated Final Maintenance Release. This because it usually takes years before we have new devices with support for a new JSR.

But I think there are many good things in JavaME area:
  • We have a Java standard in mobility area, JavaME/CLDC1.1/MIDP2.0
  • There are a lot of devices with support for JavaME/CLDC1.1/MIDP2.0
  • JavaME is OpenSource
  • The PhoneME project, an excellent piece of work is done in that project.
  • The eRCP project is also VERY GOOD for us!
I think this is not so good:
  • The JCP process is very very slow and not open for everyone. Then when a JSR is finished, it take a very long time when we actually have devices that support it and the worse thing is that sometimes no support comes at all (like AGUI).
  • For me as a JavaME developer/architect, it is not easy to understand the future for JavaME and I also don't think it help if you join the JCP (I have join JCP) to get a better understanding about it.
  • There are no devices with support for JavaME/CDC1.1/FP1.1.
  • There are delays for JSR 249: Mobile Service Architecture 2, based on JavaME/CDC1.1/FP1.1 and no public information from JCP about this delay. I can't understand why JCP don't update the schedule for each JSR.
But I think it is always nice with competition so I am positive that we now also have eRCP and soon the Google Android. I think this will help us in the future to get better Java support i mobile devices!!

I think something has to happen now in the JavaME JCP process!!
I don't think it is ok to release a JSR some years later and with no information about delays during the process, JavaME is OpenSource but it is NOT OPEN!

But don't understand me wrong, I am very pleased we have the JCP process in Java, I believe we need Java standards. But innovation I would like to see it in a more rapid way and done open to anyone.

I plan to go to next JavaOne, but I will be very disappointed if I can't find sessions about all kind of Java in Mobility area like: Android, eRCP...

1 comment:

Ken Walker said...

Good points on the JCP and additionally, specification leads must be willing to give TCKs to valid open source projects implementing the APIs so that they can claim certification!

As far as JavaOne, well we'll just have to see what sessions get accepted. Crossing my fingers.