I do not use Emacs, although I can still comment, about the specific things they mentioned. They are right it does not have to be VS Code; if you like that, th

I do not use Emacs, although I can still comment, about the specific things they mentioned. They are right it does not have to be VS Code; if you like that, then you can use VS Code. However, if you want specific features, then that is a different thing, and will have to be considered specifically. If you want JavaScript in Emacs, it could be an external extension, maybe; it probably should not be included by default. However, if the model is different enough from Lisp then it might be hard to fit; nevertheless, such an extension might help if you need to run JavaScript codes designed for other editors that do use JavaScripts, without having to rewrite them (polyfills will be possible, if necessary). Lisp alone probably isn't ideal though, and you should be allowed to write extensions in C as well (I don't know if this is already possible; maybe it is). WYSIWYG editing should have "reveal-codes" function also; without such thing, WYSIWYG isn't very good. One thing I think would want to have in text editor is capability of non-Unicode text encodings which don't convert to/from Unicode. You just should not expect that everything is conversion in one unified character set; it does not really work.