No mature, sensible code allows for 10x performance improvement (let alone...). Every time I see a statement like this I take it as a confession.
How VSCode made bracket pair colorization faster (2021)
71–80 of 247 posts
Re: How VSCode made bracket pair colorization faster (2021)
#72Earlier quoted context omitted.
That's interesting, I don't find VSCode slow at all, even when working on large workspaces via SSH over a high latency link. Sure, there are native editors that are snappier, but not to the point that affect my productivity in any way. The one thing that VSCode does not handle well is large files (e.g. DB dumps, large JSONs, logfiles), but for coding, it really is not an issue.
What plugin are you using to open workspaces via SSH?
Re: How VSCode made bracket pair colorization faster (2021)
#73No mature, sensible code allows for 10x performance improvement (let alone...). Every time I see a statement like this I take it as a confession.
Re: How VSCode made bracket pair colorization faster (2021)
#74Re: How VSCode made bracket pair colorization faster (2021)
#75If 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. 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.
Make it work, then make it fast is in most cases what you should do. I've done almost all development in vim up till 3-4 years ago before switching to vscode. It's more than fast enough for me.
Re: How VSCode made bracket pair colorization faster (2021)
#76No mature, sensible code allows for 10x performance improvement (let alone...). Every time I see a statement like this I take it as a confession.
"We improved a popular plugin by integrating it with our core application" doesn't feel like a confession to me. In fact, that's exactly what I'd like to see from an application developer. No application is perfect, and it's good when developers improve the basic look and feel of an application based on what their users want.
Re: How VSCode made bracket pair colorization faster (2021)
#77Re: How VSCode made bracket pair colorization faster (2021)
#78Re: How VSCode made bracket pair colorization faster (2021)
#79If 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. 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.
The craziest thing to me is the people who are conditioned into believing that it's not slow. I don't know if it's some sort of perverse Stockholm syndrome, or if young developers today are just not familiar with how incredibly fast desktop applications used to be decades ago. I regularly have to completely reboot it because it becomes so unbearably slow, input latency alone often reaches hundreds of milliseconds. An…
Are you still using that same computer from decades ago?
Re: How VSCode made bracket pair colorization faster (2021)
#80Earlier quoted context omitted.
That's surprising to hear, because I use vscode every day and its performance is miles away of any JS apps I've ever used. It truly feels like a native app when it comes to performance, at the same time keeping some "fluidity" of web app (like scale the entire UI with single key press or reloading the entire app like a web page). I'd say I never had issues with vscode performance and actually its performance is a maj…
For the most part I agree with you but "miles away of any JS apps" is a low bar to cross.