Why in earth would they stain their efforts with the "eclipse" name. Screenshots look great!

mdaniel 2 months ago | parent | next [-]

I in some sense empathize with you, in that Eclipse have a minor branding problem, a major discoverability problem for all of their projects of subprojects of projects to track the projects. That said, Eclipse the editor was all in on building a platform[1] upon which other people could build their own editors. It was quite popular before Electron arrived and sucked all the oxygen out of the rich text delivery space

Eclipse the IDE also sat on their laurels and got their lunch eaten by JetBrains on the functionality front and VSCode on the extensible platform front

1: <https://wiki.eclipse.org/Rich_Client_Platform/> or <https://en.wikipedia.org/wiki/Eclipse_(software)#Rich_client...>

▲

exceptione 2 months ago | parent | prev [-]

I have to somewhat defend Eclipse as the Java platform too. Twenty years ago people had hardly any RAM in their machines, and Eclipse definitely suffered for that, because without RAM you run into lots of disk i/o.

The JRE was born in a time of scarce cpu power and low RAM capacities. It has put tremendous optimization pressure on the project. I develop on .net nowadays, but I have the utmost respect of what they pulled off.

I dare you to install an Eclipse product these days. It will run circles around any Electron offering, while offering real parsers (not treesitter), and reliable code intelligence across vast source projects.

▲

bobmcnamara 2 months ago | parent | next [-]

As an embedded developer, it's still painfully slow, every CPU integration (half a dozen) are half baked, never comes with platform appropriate hotkeys, and eventually consumes enough RAM my iGPU can't allocate textures, and has been doing so since 2008.

▲

zdimension 2 months ago | parent | prev [-]

> while offering real parsers (not treesitter)

Honest question, what's wrong with treesitters?

	▲	exceptione 2 months ago \| parent [-]
		Very short answer: because a treesitter will do an approximately correct parsing, while a hand written parser will do a correct parsing (and if not, it is a bug). For a full, balanced overview, see: https://blog.jez.io/tree-sitter-limitations/