![Seth Kenlon](/sites/default/files/pictures/seth_headshot-lawrence_0.jpg)
New Zealand (South Island)
Seth Kenlon is a UNIX geek, free culture advocate, independent multimedia artist, and D&D nerd. He has worked in the film and computing industry, often at the same time. He is one of the maintainers of the Slackware-based multimedia production project Slackermedia.
Authored Comments
The article explains the "issue" (such as it is; there doesn't need to be an issue for there to be alternatives; such is the luxury of open source) but if it's not clear, perhaps going to the source is better:
https://github.com/Microsoft/vscode/issues/60
This article was written in GNU Emacs (on Linux). I didn't include it as an alternative because I cover it extensively elsewhere, such as:
https://opensource.com/article/20/2/who-cares-about-emacs
https://opensource.com/article/20/3/getting-started-emacs
I based the definition of "alternative" in this context to configuration and to plugin workflow. Even with M-x packages-list-packages, I feel Emacs has a pretty unique process for extending it, and I don't feel it would be familiar to someone looking for alternatives to VSCode. Not that that's *bad*, but I was trying to work within some constraints.