In fact, all of my blog posts is done in VS Code. I love using VS Code for programming languages like Python, and writing markdown files. What surprised me was that this editor could become pretty close to a real IDE, with autocomplete and intellisense. You were able to customize your editor with ease, whether simply installing plugins from the marketplace, or customizing your settings for your user. It was fast, clean, and highly customizable. However, once I started using VS Code, I could see why people were so into it. It was either that it was too slow for me, or had errors on startup that slowed down my productivity to a snail’s pace. Why VS Code specifically 🔗įor some reason, I always had problems with Atom. However, as I started noticing the amount of resources, especially my RAM, that IDEs can take up, I started to look for text editors that I could use when I wasn’t programming, one that I could simply use to edit the rest of my files in my projects, such as markdown files. As for me, although I dabbled in Atom, I didn’t really customize it too much, nor did I install a lot of packages. The fact that it is so customizable, yet does not take up the same amount of resources as an IDE makes it the perfect editor to use and personalize. Why not Atom 🔗Ī lot of people know about Atom, and its extensions that are able to be installed via its package manger apm. I recently came across it and decided to give it a try.
At some point in time, you may have heard of VS Code, or Visual Studio Code, as an open source competitor for Atom, backed by Microsoft.
0 kommentar(er)
