...and therefore I don't think he gets Ajax either.
I feel bad for Chris
-- I'm sure what he was trying to say
made sense in his head
, but it just came out as a spew of ignorant and defensive drivel. I would expect more from a CEO.
Chris has made the mistake of thinking of Eclipse as just
the "champion of the heads-down Java server programming world" (sic) and missing everything going on around it. That's soooooooo 4-year-ago thinking.
Chris, there are two dimensions to Eclipse. The technology and the ecosystem.
On the technology front, there are over 80 projects
with many great exemplary apps - he's stuck on one. Take a look at what's going on in the CDT
project and with DLTK
. Chris mentions a goal of "democratizing development" -- he should look at the BIRT
project whose primary interface is a pretty darned intuitive Report Builder, so simple even an MBA can figure it out. Yes, of course there is still lots of "Java server" programming projects but it often relates to OSGi
. For example, the EclipseLink
project - which is from the Oracle TopLink family. I'm sure Chris remembers TopLink.
Then there is the Ecosystem. Eclipse enables innovation networks. Look at the CDT project -- lots of contributors, lots of innovative products
. Eclipse is a factor in many parts of the supply chain of the Embedded world because of it.
I would never be so arrogant to say "Ajax needs
Eclipse" like Chris implies, but let's take a step back and generalize. Take a look at this slide on why the Software Development Model
is broken. Hypothetically speaking of course, imagine if Chris's development team went off and spent god knows how long building useless "infra" with little or no differentiating value. Maybe in some relatively unpopular programming language with all kinds of gnarly embedded proprietary APIs that would be very difficult for his new hires and acquisitions to learn and extend. Meanwhile, Chris's competitors are competing on a common platform
, building with well known tools and APIs (making hiring and acquisitions easier) and tapping into a developer mindshare that Evans says
is over four million people. Seems like a more successful proposition.
Chris claims that Eclipse is an "evolutionary dead-end" from a "web 2.0" perspective. Tell you what - I'll report back in a year on the progress of the Members participating in the Eclipse Ajax ecosystem, and he can do the same for Active Grid, and we'll see who's ahead, and who's dead.