Why is it that MIDP 2.0 decided to completely lock homebrew developers out of J2ME development? If you read this first you'll notice some people are annoyed at the way root certificates are handled, mainly that there is no certificate that is guaranteed to be available on every device, and the way Java Verified is per-device. This is a big problem.
Another problem that I have been having lately is that of free software and J2ME. Now you may ask why can't you just put up with a few security prompts for your hobby projects? Sure, I am fine with that. As long as they are few. The problem here is of course that they are not few! If you want to, for example, read maps from a memory card you could be reading from hundreds of tiles.
I think the problem here is that the APIs are actually becoming useful, and the security prompts for these sort of applications are becoming a big bottleneck, necessitating signing. But there is no way to sign anything for free! Not as far i know, anyway. You are also not allowed to import your own root-certificate.
I think security is a good thing, but locking out power-users is also bad. This while things is putting me off my long-needed phone-upgrade.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment