Re:VSCode rebrands as "The open source AI code editor"
by bobajeff on Sunday December 28, 2025 @11:00AM
(#46411977)
Thanks, it's been so very long since I've tried emacs. I remember I didn't like how it looked. So I used vim instead. (There was no vscode back then.) So I never did give it much of a try.
Emacs might be a solid editor choice but my intuition is that it probably won't be worth it for the same reason LiteXL wasn't for me. If I do work on adding features to my editor I think I'd be more comfortable doing it in js, html and css. And if possible I'd rather start with a base that's mostly where I want it to be. Trying to turn emacs into vscode sounds like way more of a project than turning Theia or CodeMirror into vscode.
Re:VSCode rebrands as "The open source AI code editor"
by f1shy on Monday December 29, 2025 @11:28AM
(#46422224)
Actually there are plenty of packages already which can near Emacs to VSC or Sublime in look and feel, and imho go circles around the 2 in functionality.
Re:VSCode rebrands as "The open source AI code editor"
by bobajeff on Tuesday December 30, 2025 @10:11AM
(#46434051)
Care to link to those? I looked and all I found was this:
https://github.com/DevelopmentCool2449/visual-emacs
Which didn't really impress me terribly much.
You are right that VS Code has a "nicer" out of the box UX (this is subjective of course), but Emacs offers a malleable environment. In VS Code, you are limited to what the APIs the developers decided to expose. If you want a specific behavior that isn't supported, you either fork the editor or create a feature request ticket and wait for someone to prioritize it. In Emacs, because you have full access to the internal runtime, you can implement that feature yourself in a couple of lines of Lisp.
1: https://kristofferbalintona.me/posts/202505291438/