Pulsar (former Atom) is still the best code editor in my opinion. It is easiest and fastest to use, has all the nice productivity boosting plugins and is overall great for all the same reasons the Atom was great. 🚀
See also [email protected]
Pulsar (former Atom) is still the best code editor in my opinion. It is easiest and fastest to use, has all the nice productivity boosting plugins and is overall great for all the same reasons the Atom was great. 🚀
See also [email protected]
Had a distinguished collegue (from the Bell Lab days) say to me recently:
“IDEs take up a lot of RAM on my machine. Vim takes up a lot of squishy RAM in my head. I need squishy RAM to hold info relevant to problem solving, not options available in my tool chain.”
While I agree with the sentiment, the key bindings have been burned into my less squishy ROM at this point, and I’ve got all banks of squishy RAM available 😄
hahaha good point.
That colleague, keep in mind is a bit older, also has Vim navigation burned into his head. I think where he was coming from, all these new technologies and syntax for them, he much rather prefers right clicking in the IDE and it’ll show him options instead of doing it all from command line. For example docker container management, Go’s devle debugger syntax, GDB. He has a hybrid workflow tho.
After having spent countless hours on my Vim config only to restart everything using Lua with nvim, I can relate to time sink that is vim.
@varsock @otto
Oh god yes! Each instance of VS22 takes up more than 1Gb of RAM - what I’m doing right now with this piece of code does NOT need 1Gb of memory! Have they not heard of lazy loading?
Vim doesn’t take any thought for me, it’s all muscle memory.