In a post from couple of days back, I blogged about the massive market that Nokia has announced for J2ME applications. The comments on that post are mostly pessimistic. Most developers are unhappy with the state of J2ME, with anger directed towards Operators, Manufacturers and Sun equally.
Any J2ME developer knows that the promise of write once and run anywhere, like the J2SE promise, is based on marketing genius and little, if any, factual grounds in reality.
Java ME (or J2ME whatever you prefer).
Ok, so it isn't new and it isn't perfect.
Yes, I am confused about which way to go with Java.
I just read this article .
On one hand, the keepers of the Java flame are making the language harder and harder to understand and use (Generics anyone?).
Nokia has released a proposal for creating a new project in Eclipse for mobile phone development tools.
For some time now I went on the Agile programming bandwagon convinced that it was the next best thing since sliced bread. After a sustained year of practicing it, I am off the wagon.
A roundup of activity in the JCP J2ME world.
New API's that have been proposed:
RTSJ version 1.1
This API aims to fill some gaps in the Real Time Specification for Java as far as J2ME is concerned
API's that are in public review:
Mobile Service Architecture for CLDC
New API's that have pa
Nokia has decided to join the Eclipse project as a board member and a strategic developer, whatever that means.
Sorry, I know what it means. a) it gives Nokia veto power over Eclipse's J2ME environment and b) it allows Nokia to push its own developer tools for J2ME development.
I know that a large percentage of J2ME development is targeted for the Nokia devices.
Two blog entries have made me come back from work induced blog hibernation. First, Chris bloged about how Coding skills are no longer enough in his daily blog.
According to ZDNet,
Cisco is to consume Nokia
This, on the same day that Hackers hit Cisco.