Re: What Are Your Java ME Pain Points, Really?
Posted: May 29, 2007 11:45 PM
What I missed here in the discussion a bit:
How big is the learning effort to write an application?
Where do I find an adequate and free VM for my device (if not delivered as "batteries included")?
How would I setup a development environment?
Where do I find tutorials to start programming?
And: If carriers are restricting me to write applications for my own device, I would give up.
What drives Java in many ways in the SE and EE world is the openess. Everyone with a particular skill can contribute in some way. Look at Sourceforge and other repositories and you find at least usable snippets for everything you can think of.
Codes people have written in their spare time, to solve their own little needs, and easily shared that with others, who, if they found it not usable out-of-the-box, adapted it for their own environment.
But for me, I until now never successed in writing an application for at least my own device to share it with other users of the same type.
The entry to ME development (see questions above) was all in all too much effort for only a bit of fun programming.
And if I would need a certificate to run my own little Memory game calculator on my own mobile device, this would additionally be a knock out criteria.
I see the need for WORA and for setting up a complicated build process including many test devices for professional development.
In a more open scenario, one would write an application for his own device, and others would adapt it for theirs. So the Run-Anywhere would be a community result, not a requirement in first place, which no amateur could fulfil.
Young people learn to program Java in school lessons, and sometimes write interesting programs for scientific topics in project groups.
Could you imagine ME development at school?
"Well done on your Nokia, Peter, but let us see how Thomas managed to make it run for his Sony..."