|
I find this questionnaire very interesting because I have a rather broad definition of fragmentation. To me, fragmentation not only includes API and implementation fragmentation, but issues such as signing, testing and certification requirements, distribution, etc. Because of this, I think that no one group can "solve fragmentation", but that it needs to be divided into pieces and that every one of the above groups has plenty of work to do.
For years, we've taken a decentralized approach to addressing these different areas of fragmentation. Some groups have done better at it than others, but overall, progress has seemed glacial. If insanity is defined as "doing the same thing over and over and expecting different results", then maybe we should try something different, like a more centralized approach.
Finally, for all the hype that Java ME fragmentation gets (and fragmentation is not a problem exclusive to Java), we have to admit that it is a by-product of the platform flexibility that has allowed ME to be deployed on more mobile devices in the world than any other application execution environment. While it is not possible, nor advisable, to eliminate every type of fragmentation, platform differentiation cannot be used as an excuse to avoid collaboration against fragmentation that leads to duplicative and wasteful effort.
|
java.net RSS Feeds
