It’s something you can totally deal with – at least at the scale of my projects. I do run Windows 10 and the input delay when typing inside VSCode is not that much slower than typing in Notepad or an Explorer window so I would say that’s very good.ĬTRL+P searching is slightly slower in VSCode but it’s not slow enough where it’s annoying or getting in the way. The largest applications I work on tend to have hundreds of files and tens of thousands of lines of code and moving around files feels very good in both editors. However, once both applications are up and running I can’t say that VSCode is much slower than Sublime Text for the projects I work on. It starts up almost instantly and VSCode takes around a solid 1.5 seconds to start on an SSD with an i5 3.2GHz CPU. When it comes to using a code editor, there are a number of things you can judge it on such as performance, stability, looks, feel and its extensibility. To take an editor I’ve been using for many years and just throw in the garbage as if it were moldy pizza crust is a pretty big deal, but I switched because the pros out weighed the cons. To my surprise I uninstalled Sublime Text 3 after about 5 hours and have been happily using VSCode for the last month.
With that said, it’s been about 8 months since I last tried VSCode so I thought I would try it out again. That means when something new or better comes along, I tend to have very little emotional attachments and jump ship. I’ve been using it for years for full time code development and writing.īut I would also consider myself to be a pragmatic programmer with very little brand loyalty.
Read why I switched to VimĪnyone who knows me knows that I’m a huge fan of Sublime Text. In Mar 2019 I switched to using Vim because VSCode was too inefficient for writing.
0 kommentar(er)
