Split on support for 'old' Java in next Eclipse
Embedded developers like it old skool
The dispute is over whether to focus on Java 5 or to continue supporting its aging predecessor Java 1.4. Eclipse projects currently embrace several versions of Java ranging from 1.4, released six years ago, to the latest Java 6.
At the heart of the matter is the issue of "bloat" - whether later versions of Java have become choc-full of APIs for every single scenario, and whether Java should be stripped down to the bare essentials.
A "large portion of the community" making up the recent E4 summit was reckoned to be "resistant to using old technology", according to the architectural foundations wiki record of the E4 summit.
It's those pesky "embedded folks (and their ilk)" that apparently do not want Java 5 because they are worried about "bloat" the wiki said.
There no elaboration on the differences between the camps, but embedded developers in general would likely have preferred a version of Java suited to deployment in devices that have limited memory and processing power or rely on extremely fast performance. More APIs can make this fit difficult and also slow system execution.
Software leaders including C++ inventor Bjarne Stroustrup and the founder of the open source Spring Framework Rod Johnson have also weighed in, in the past, on whether Java is becoming unfit for action.
Java 1.3 ... Java 6
Write once, run anywhen ?
1.4? That would be nice.
We develop an API and still have a number of clients still running Java 1.3 - and last month got an email from a corporate client who was still running 1.2! This is J2SE as well.
There is no good reason to support ancient Java versions in a new Eclipse version - those who need support for an old version can obviously run an old version of Eclipse. It is not like those poor sods who use Visual Studio and discover that it is impossible to buy the old version they have to use for their legacy code.