Making Visual Studio Code Look Nice(r) Themes Since I first wrote that post some features in Atom changed, as did my needs, so this post won't stick entirely to the original. To do this, I refer mostly to the original post and recreate the same sub-headings and needs. On initial inspection, it's still more optimized for coding than writing, but I thought it was time I dug into to how it compared to Atom from a writer's perspective. Atom has vastly improved since that post, but still suffers from a lot of reliability, memory, and CPU issues, thanks to the fact it's built upon web technologies, not native code.Īlso since that post, Microsoft released Visual Studio Code, that, despite having similar origins to Atom, somehow feels more polished and is more performant. At the time I was looking for a text editor that was extensible, open source, and that I could optimize for a writers setup, not just for coding. Some time ago I wrote a post on how to configure the Atom text editor for (technical) writing that proved one of my most popular posts.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |