Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] Two debug toolbars
Well said Greg. From the discussions I've had with the e4 team, this seems to be the case. In fact I was told what I wanted do to with the Momentics toolbar couldn't be done because of the compatibility layer (mind you it seems to be working just fine). And the RCP gang do love e4 as they should because of that kind of flexibility.

But you are definitely correct about the need for the IDE community to step up and take control of Eclipse the IDE. We've become complacent about it. I'm very curious about why that is and how we can fix it. For example, if you were given full write access to the Eclipse platform today, would you dive right in and fix what bothered you, especially if you didn't need to wait a year to have those fixes in a release?

Other IDEs are catching up and continue to evolve. Our desktops continue to evolve. Eclipse the IDE is starting to look really old. People are getting really tired with dealing with workflow issues, a lot of which we've been fighting since day 1 of the CDT. But these things won't get addressed by themselves. We need to figure out how to energize the community to really care about this.

Doug

From: Greg Watson <g.watson@xxxxxxxxxxxx>
Reply-To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Date: Tuesday, 18 June, 2013 4:23 PM
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Subject: Re: [cdt-dev] Two debug toolbars


On Jun 17, 2013, at 12:57 PM, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:


On Mon, Jun 17, 2013 at 7:04 AM, Greg Watson <g.watson@xxxxxxxxxxxx> wrote:
If only 1% of those committers devoted some time to working on the platform, maybe some of these bugs would get fixed.

I would accept this argument if the issues we are discussing were not regressions. People who decided that e4 was the best way to invest limited platform development resources have to take full responsibility for the consequences of that decision.


I suspect the issue is that the e4 work was primarily driven by the RCP community, for which it presumably works well. It's the compatibility layer that is having the majority of problems, and there doesn't seem to be any interest or motivation in fixing them. It seems like this is something the IDE community is going to have to do themselves…

Greg

Back to the top