Emergence of Web 2.0 and Software as a Service (SaaS) - Are they threat or opportunity to the growth of Eclipse?

Manu Kuchhal (IBM), David Klein (IBM)

Emerging Technologies · Birds Of A Feather

Tuesday, 20:45, 1 hour 15 minutes | Room 209/210 | Download in iCal Format

7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18
·
19

Manu Kuchhal

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?

Eclipse RCP positioned Eclipse as a Virtual Client-side OS that provides a convenient environment to build, run and host platform neutral Client side applications. These applications get deployed on user’s machine, exploits the local resources such as CPU, graphics library, network etc to provide Rich User Experience. Eclipse RCP played very important role in motivating enterprises to shift from browser to client machines as the environment to run their user applications. Growth of Web 2.0 style of application development on the contrary again puts browsers back into the main focus. There are technologies such as Dojo/Ajax etc which have gained popularity in recent time and seem to be providing almost similar degree of richness as done by RCP. Developers are again motivated to develop their applications as widgets written in Javascript as opposed to Eclipse Plugins written in Java. Does it dig into the market of Eclipse as a Rich Client Platform?

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.

Floor Plan

Gold sponsors

BEA logo

IBM logo

Wind River logo

Replay Solutions logo

JBoss logo

SOPERA logo

Cloudsmith logo

BIRT Exchange logo

Skyway Software logo

Oracle

BlackBerry logo

AMD logo

Silver sponsors

Sybase

Google

Genuitec

Instantiations

Teamprise

Telelogic

Innoopract

Business Objects

LynuxWorks logo

Hardware sponsor

AMD logo

Media sponsors

Extension Media

Methods and Tools

ACM

Addison-Wesley logo

SD Times logo

Open Systems Publishing

Software Test & Performance logo

SDForum

Be a Sponsor