I think it's strange that they think that commoditization might be bad for J2EE.
If anything, commoditization is good: it's good for the customer because there will be more direct competition and thus lower prices, and it's good for the developer because we can write to one standard and still give the customer a broad choice in deployment platforms.
It might be bad for those writing proprietary J2EE platforms, but they're a pretty small part of the community as a whole. I suppose it might be bad if they managed to start adding a whole bunch of things to new versions of J2EE through the community process.
The problem with commoditization is that there is little incentive to improve your product. If one product is the same as another then the only thing that differentiates thme is price. Companies that make great products find it very difficult to compete on price because their products cost more to make. The best companies learn very quickly to abandon a market as soon as the products in that market are commoditized.
This isn't really meaningless drivel. This thread probably belongs in Java News.
Where-ever it belongs, I saw (or didn't see) something this weekend, that surprised me. While browsing around Barnes and Nobles book store I invariably wander over to the programming aisle. If for nothing else, just to see how many books are written on exactly the same topic. :roll:
B & N has had a whole section of the programming aisle devoted to Java for years. Its gone! C, C++ & C# have a section. .NET has a section. etc. etc.
Has anyone noticed this, as well?
Anxiety does not empty tomorrow of its sorrows, but only empties today of its strength. – Charles Spurgeon