This session was with Paul Su and Lakshmi Dontamsetti from Aplix, and Óscar Gutiérrez Isiégas from Vodafone.
When talking about MIDP3, I always get this feeling of it being a little too late. Now, the core development of numerous applications and games that I have worked on has been primarily j2me MIDP2, so I am certainly not anti j2me, but its advantages are slowly being eroded away by different platforms. I don’t think j2me is going to disappear, but I think its never going to fit the bill of its original testament (write once, run anywhere), and what surprises me is that there isn’t more being done in MIDP3 to reduce future fragmentation (they are doing some work to solve this though).
My biggest issue with j2me is probably its signing process, and security model. As far as I’m concerned the whole thing is broken. According to Paul Su, this is out of the scope of MIDP3, so it looks like nothing is going to change. The only solutions that have been introduced to solve the certificate fragmentation, involve spending a shit load more money (and infact do not really solve the problem completely). I am talking about Java Verified of course :)
There are alot of useful new features coming into MIDP3 though, and I encourage you to take a look at the slides to see a quick overview.
Posted: April 7th, 2008 under Conferences.
Comments: none