zlacker

>>michid+(OP)
I love vscodium but more and more I worry about how Microsoft is effecting it down stream. To the point where I'm actively looking into making my own editor. I'm putting it off for now but I'll probably start playing around with Theia and Codemirror on the side just in case.

>>bobaje+Z1
If I have to bet, I will absolutely go for MS enshitifying it beyond reasonable usability, in one way or another, more soon than later.

Making an editor is anice endeavor. But there are plenty of, which are extremely well developed, open source, in many directions, emacs and vim the most prominent. But many others out there.

>>f1shy+A6
Emacs and Vim are terminal based though. So nice things like scroll bars, tabs, drag and drop etc. might be available as hacks but will disappoint in the ways in which they fail to work like a actual GUI interface. I'm also not a fan of model text editors.

For open source GUI text editors there sadly aren't many that match the feature and polish of vscode.

>>bobaje+da
While Emacs can run in a terminal, it is more widely used as a GUI application that can render images, PDFs, variable-pitch fonts, handle mouse support (drag-and-drop, menus, scrollbars), and even work on touchscreens such as on Android [1].

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/