I wouldn't call anything based on Electron "lightweight".
My completely subjective list of text editors in order of lightweightness:
Notepad2 - a feather
Notepad++ - a dog
VS Code - an elephant
Eclipse is like that one Russian aircraft carrier.
I think you can go either way with vscode similar to the whole vi vs neovim with tons of plugins
I was quite surprised, when I recently used VS for a small C project, at just how snappy it was for that project compared to VS Code for the same project.
I then compared it to VS Code for a larger C# project and it still compared very favourably in terms of responsiveness and speed.
I think a lot of people using VS Code are comparing small projects in VS Code to large projects in VS and concluding that it's VS that is the problem.
I just discovered Notepad3 [2], which appears to be a maintained fork. Screenshots look very similar to Notepad2. Gotta check it out later.
Any other forks that I should be aware of?
(I personally ditched n++ because the shell highlighting false-positives errors, and syntax errors are especially ugly in the default scheme. And it wasn't on GitHub back then, so complaining would be a chore.)
The funny thing is that my N++ instance has ~5 files always opened, 3-4 of those buffers and when they get to 6 or 7 I trim them down to 3-4. This is probably the beginning of why we find people doing weird things...
There are
- text editors
- programmers text editors
- integrated development environments
- rapid application development tools
Sorted by size, reversely proportional to feature set. Basically VSCode is an overbloated #2, that isn't good enough to be #3 and is nowhere near #4.
You could've fit a full blown RAD into 500MB (Borland C++ Builder) 20 years ago.
I use both. NP++ for like single documents or quick kanban lists for myself. VSCode is better for a group of closely related items such as when using it as an IDE. As I do not keep both open all the time NP++ usually wins on startup speed. Which fits my workflow.
It's about normal.
It's also why Rust is struggling to eat into C and C++ marketshare - the class bugs it prevents has such a tiny footprint compared to all the bugs present in any given C and C++ system that it doesn't motivate the developers to spend the time Rust requires to ramp up to speed on a new language, and then use it in production.