| [News.eclipse.foundation] Re: E4 / SWT 4.0 |
"Eric Rizzo" <eclipse-news@xxxxxxxxxxxx> wrote in message news:g2bv8e$qd0$1@xxxxxxxxxxxxxxxxxxxxFrancis Upton (News) wrote:I definitely recognize that (and I think many other people do, though certainly not everyone who enters his own wish list feature requests). However, while we hear from one side of the collective project mouth that more contributors are needed, we hear from the other side of its mouth how they are spending all this time and effort on e4 planning. Well, if you have a backlog of bugs and enhancements to an existing code base, the prudence of moving resources in such critical shortage to a completely new effort is, well, debatable IMHO. Look at Micro$oft's history (and the reason many of the MS-haters are haters) for an example.
*We need more people doing the work*; it really does not matter if they are committers or if they are contributors.
I am not sure what exactly you had in mind, but to me, comparable situations in the history of Microsoft were when they decided to develop Windows instead of sticking with MS-DOS, or when they completely redesigned Windows 3.11 and went to Windows 95 to make it easier to use, or when they decided to move everything over to be based on Windows NT to improve security and reliability. Would you rather that they perfected MS-DOS, or Windows 3.11, or kept developing Windows 95/98/ME?
There are lots of examples like this in the computing world. Do you think Apple would still exist if they had continued to fix each and every bug in Mac OS 9 rather than making a cut and moving everybody over to Mac OS X with a solid BSD base? Don't they screw everybody over again by discontinuing Carbon and making Cocoa development a requirement? I am sure they haven't fixed all the bugs in Carbon before they moved their developers over to Cocoa.
The reason we are working on e4 as well as (not instead of!) the 3.x stream is that we believe that Eclipse as a component integration platform will not exist five or ten years from now unless we re-invent it in a way that makes Eclipse relevant to programmers using other programming languages, developers working on distributed applications, and users who would like to see (parts of) the functionality they use in an Eclipse-based desktop application in a browser. We will not achieve all of these goals within the next few months, but I think they work well as a vision for what we are aiming at.
Eric