|Re: [ide-dev] Java IDEs comparison|
From: <ide-dev-bounces@xxxxxxxxxxx> on behalf of Bruno Medeiros <bruno.do.medeiros@xxxxxxxxx>
Reply-To: Discussions about the IDE <ide-dev@xxxxxxxxxxx>
Date: Wednesday, September 14, 2016 at 10:34 AM
To: Discussions about the IDE <ide-dev@xxxxxxxxxxx>
Subject: Re: [ide-dev] Java IDEs comparison
I think people are missing the point on this. Yes, Eclipse 4.0 and 4.1 were buggy as hell but we didn’t officially cut over until 4.2. I’m not sure how many users actually experienced those versions. And at the end of the day, the Eclipse Workbench used by the IDE is barely e4 anyway. There is a massive amount of legacy code that still works with the old APIs (see CDT, etc).
And that was a long time ago. I’d expect a blip but the trend continues. Ian Bull raised probably the best point. Eclipse 4 also co-incided with a massive drop in investment from IBM. In fact, e4 was an attempt by the fine people there at the time to grow the community to make up for that shortfall. Not sure it actually worked, but that’s how I remember it from my front row seat. I felt really bad for them actually, but we are where we are.
It also gave birth to the Eclipse Marketplace, tycho maven builds, product aggregation, Check for Updates. Can you imagine Eclipse without an install system like this? I can’t, or we’d be complaining about the lack of one.
LOL, I think the people who think Eclipse 4 is ugly, think so because it’s outdated compared to other present day desktop tools. I’m not sure the Classic Theme helps with that. It just makes Eclipse look older, no?
Yes. After I said that, I have volunteered to help facilitate the UX group sponsored by the Architecture Council. So I’m putting my money where my mouth is. I hope everyone here who has great opinions and ideas to move the vision for Eclipse forward will come help.
Back to the top