How responsive are Java vendors to your requirements? Where should the line be drawn between standardization and competition in the Java market? What role should the JCP play in the process?
Java Standardization vs. Competition: Developer Input Carries the Most Weight
Although what's easiest for the Java developer isn't necessarily what's most desirable for the Java vendors, they recognize that the next great Java API will emerge from the mind of a developer.
by Glen Kunene
January 28, 2004
n the Java market, "write once, run anywhere" standardization is the carrot and the threat of .NET adoption is the stick. Which is the greater motivator depends on the vendor's standing in the market. For the leaders, standardization may negate the differentiators that have made their products popular, so their attention may be more focused on competing with Microsoft. The Java vendors playing catch-up, meanwhile, recognize that standardization can level the playing field for their products.
The good news for programmers is that every vendor, regardless of market standing, must first and foremost meet the requirements of its customers (i.e., Java developers). With several major product releases announced by Redmond last fall at its 2003 Professional Developer's Conference, no Java vendor can risk leaving its users unsatisfied.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!