zlacker

>>michid+(OP)
This pivot sounds like VS Code is moving from a text editor to a thin client for AI services that Microsoft wants to push. It is one more step towards a future where our development tools (just like everything else on our computers these days) are just thin clients/wrappers around SaaS.

Emacs remains the antidote to this. I use Emacs because I want to remain the architect of my development environment, not become the consumer of a telemetry-gathering platform architected by PMs at a big tech company. It is also an absolute joy to use an environment that provides you with the same amount of power as the core maintainers, allowing you to fully inspect and modify the system even while it is running.

>>achyud+9p
My path in the emacs/vi divide forked a lifetime ago, and emacs is so fundamentally different that it was never worth sacrificing the massive productivity vim gives me to dip back into emacs

But maybe that should change. I like vscode for when I need more IDE features than I care to cobble together with plugins.

I don’t need another subscription in my life. Especially for anything I rely on.

>>mingus+1s
I was more familiar with Vim bindings and relied on Vim emulation layers in various IDEs before I moved to Emacs. Evil mode and Doom made the jump possible without sacrificing too much productivity. With Evil, I didn't have to retrain my muscle memory and with Doom I didn't have to cobble together a functional config from scratch.

After a couple of months of using Doom, I felt comfortable enough to roll my own config which also helped me better understand how things worked at a lower level. More interestingly, after a couple of years, I transitioned from Evil to standard Emacs bindings as that felt better integrated with the rest of Emacs.