Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] Towards a simpler(-looking) Java IDE

Hi,

I personally think that having lots of language/platform/etc specific tooling (especially for Java) and adapting to concepts specific to the language is one of the things Eclipse is pretty good at (Eclipse for Java development really feels like an IDE written for Java) so I'm reluctant with the idea of removing specific perspectives like the Java one, especially since a lot of the ecosystem around Eclipse (e.g. plugins or RCP apps having their own perspectives) also relies on that.

In addition to that, I feel like making changes like that "globally" (e.g. moving a way from language specific perspectives) require effort from all relevant projects including projects not maintained by the Eclipse Foundation causing the changes to never actually happen. One reason I like making a new simplified perspective (or alternatively removing items from the existing perspectives by default) is that this can be done incrementally (e.g. first creating the new perspective and make it as obvious as possible for users to switch to it, then featuring it prominently (as far as this is reasonably possible) and eventually making it the default).

That being said, I am unsure how good of an idea it is to "copy others". I guess the way how perspectives currently work is something many existing Eclipse users like and making it easy for users to switch back when they don't want these changes is probably important (including the ability to keep their existing customized perspectives). Just because something works for VSC or IntelliJ, that doesn't mean it would work well for the Eclipse ecosystem.

Yours,
Daniel 

On 04/01/2026 15:19, Mickael Istria wrote:
Hi Daniel, all,
 
The topic of making the IDE feel more simple has always been a long discussed one. All the points you mention are entirely valid, some of them were already discussed and have history on mailing-lists or bugzilla, some of them are new.
For a more general approach to this problem, I would personally also strongly question the existence and usage of the Java perspective, particularly if you start with a comparison with VSCode. VSCode has 5 kind-of perspectives: Explorer, Search, Team, Run/Debug and Extensions. The Platform already provides Explorer, Team and Run/Debug ones. VSCode has no language-specific perspectives, because overall developing in language X is the same activity and requires the same workflows and tools than developing in language Y, its perspectives are language-agnostic enough (so is Eclipse's Project Explorer).
So from here, I would personally recommend that if one wants to push the Eclipse IDE into a fresher look and feel, deprecating and stopping usage of the Java perspective and other language-specific perspectives all together in the packages would probably have a better impact than adding yet-another-perspective to the long list of existing ones. Adding UI elements and giving more choice to users is rarely perceived a UI simplification, people tend to prefer guidance over choice.
 
Another aspect where VSCode differs in the absence of "main" toolbar. This can work with Eclipse IDE too, there is already an option for that, and Ctrl+3 in Eclipse IDE maps the Ctrl+P in VSCode well. Disabling the toolbar by default wouldn't be so hard to do. Sure, some users would be disturbed at first sight; but those could reenable the toolbar easily if they want.
 
I personally have made my Eclipse IDE mimic VSCode on all those aspects (start from an SDK to avoid Mylyn and other useless extensions that come with EPP package, removed toolbars, minimized open views, perspective switch on the left with only Project Explorer, Debug and Team) and the experience is very good IMO, and I've seen people impressed by the simplicity of Eclipse IDE when looking at such configuration and comparing it with the memory of how "cluttered" Eclipse was to them when they were users. The Eclipse IDE is fully capable of achieving similar simplicity already; the question is more how much the maintainers community is ready to push "disturbance" to its users to make simplicity a priority over conservatism.
 
Cheers

Back to the top