Eclipse started off as an IDE that runs on every developer’s workstation. Software as a Service (SaaS) calls for making all possible kind of applications available as services to their users, even perhaps development tools too. And these services are often rendered on-demand to the user's workstation. So, does it dig into the market of Eclipse as an IDE in its current form?
We all know that there are number of attempts made by almost all vendors to make their Eclipse based offerings coherent with Web 2.0 and SaaS requirements. But can Eclipse community adopt an approach with certain degree of mission and co-operative thinking behind it. Eclipse has history of re-inventing itself and getting itself relevant for new usecases from time to time. Are there other perspectives or approaches which could be taken by Eclipse as a whole to not only survive but flourish in this emerging paradigm?
We could use this session to think over some of the possible steps which Eclipse Community could take in this direction. I am sure many will completely disagree with entire content of this proposal and will not agree with the need of such a brain-storming; however I do believe there might be few who will be interested in this session. Any takers?? :-)
Manu Kuchhal is an Advisory Software Engineer with IBM Lotus at the IBM India Software Labs. Manu has been evangelizing OSGi/Eclipse for most part of his career.
Past 7 years working initially with OSGi, and then Eclipse technology as part of the development team for IBM's Eclipse based Expeditor platform.