Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ui-best-practices-working-group] [ide-dev] Working sets (WAS: Re: Java IDEs comparison)

On Thu, Sep 15, 2016 at 4:15 AM, Doug Schaefer <dschaefer@xxxxxxxxxxxxxx> wrote:
+1. That’s been discussed informally here and there. Having a single committer list for the entire IDE at Eclipse would help. But we’ll always have to deal with important projects that aren’t at Eclipse, like Pydev and Nodeclipse. We need to get better at influencing anyway.

I think this might be a case of leading by example. Right now, the examples given by the IDE are cluttered. We used to do separate perspectives per language. I din't find it bad thing back then. Today I find myself using three perspectives at most - one for development, one for debugging and one for Git repository management. Man it would be so cool if we would be able to gather that data from the thousands of users out there. We are just flying blind and guessing. :)

For now, I don’t think it’s worth it.

I think the risk is damaging the ecosystem of plug-in developers if we continue with the status quo. It's really confusing right now. There is no clear guidance on what the path should be. Yes, the actual immediate user benefit of the work is hard to quantify/justify.



Back to the top