3 ms·

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 th

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.

zdimension 1y ago
> while offering real parsers (not treesitter) Honest question, what's wrong with treesitters?
- exceptione 1y ago
  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/ https://blog.jez.io/tree-sitter-limitations/
bobmcnamara 1y ago
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.