<story><title>How VSCode made bracket pair colorization faster (2021)</title><url>https://code.visualstudio.com/blogs/2021/09/29/bracket-pair-colorization</url></story><parent_chain><item><author>fragmede</author><text>What CPU do you have? Because even though VSCode is &amp;quot;just&amp;quot; a text editor, I&amp;#x27;ve found it&amp;#x27;s relatively demanding. A Core 2 Duo, which is admittedly a little old, but which does &lt;i&gt;absolutely&lt;/i&gt; fine with vim, is slow to the point of being unusable with VSCode.</text></item><item><author>vbezhenar</author><text>That&amp;#x27;s surprising to hear, because I use vscode every day and its performance is miles away of any JS apps I&amp;#x27;ve ever used. It truly feels like a native app when it comes to performance, at the same time keeping some &amp;quot;fluidity&amp;quot; of web app (like scale the entire UI with single key press or reloading the entire app like a web page).&lt;p&gt;I&amp;#x27;d say I never had issues with vscode performance and actually its performance is a major factor why I use it.</text></item><item><author>voz_</author><text>If you can make something 10k x faster you didn’t so much fix it as just switch it to working correctly as it should have in the first place.&lt;p&gt;VSCode is a good tool, but it’s unbearably slow, and it breaks my heart that so much development has converged on something written in electron with such a low regard for performance by any measure.</text></item></parent_chain><comment><author>bick_nyers</author><text>I think unfortunately a CPU from 2008 just isn&amp;#x27;t gonna cut it here. Single thread benchmarks core for core have risen about 4x since then, average core counts have risen 4x, and L3 caches were added. Probably SIMD instructions are a consideration here as well.&lt;p&gt;That being said I&amp;#x27;m a huge fan of prioritizing longevity of computer parts versus constantly upgrading and generating e-waste.</text></comment>
<story><title>How VSCode made bracket pair colorization faster (2021)</title><url>https://code.visualstudio.com/blogs/2021/09/29/bracket-pair-colorization</url></story><parent_chain><item><author>fragmede</author><text>What CPU do you have? Because even though VSCode is &amp;quot;just&amp;quot; a text editor, I&amp;#x27;ve found it&amp;#x27;s relatively demanding. A Core 2 Duo, which is admittedly a little old, but which does &lt;i&gt;absolutely&lt;/i&gt; fine with vim, is slow to the point of being unusable with VSCode.</text></item><item><author>vbezhenar</author><text>That&amp;#x27;s surprising to hear, because I use vscode every day and its performance is miles away of any JS apps I&amp;#x27;ve ever used. It truly feels like a native app when it comes to performance, at the same time keeping some &amp;quot;fluidity&amp;quot; of web app (like scale the entire UI with single key press or reloading the entire app like a web page).&lt;p&gt;I&amp;#x27;d say I never had issues with vscode performance and actually its performance is a major factor why I use it.</text></item><item><author>voz_</author><text>If you can make something 10k x faster you didn’t so much fix it as just switch it to working correctly as it should have in the first place.&lt;p&gt;VSCode is a good tool, but it’s unbearably slow, and it breaks my heart that so much development has converged on something written in electron with such a low regard for performance by any measure.</text></item></parent_chain><comment><author>wenc</author><text>I used to run vim and VS Code on a Core 2 Duo from 2005. Vim is a lot faster but VS Code is so much more powerful — it’s a full featured IDE. It’s not a quick and dirty text editor like Kate. It’s not meant to be that. I still use vim to edit config files but for everything else I use VS Code.&lt;p&gt;I’ve since upgraded to a 2014 i7 and now VS Code feels fast.</text></comment>