Live data from Hacker News

How VSCode made bracket pair colorization faster (2021)

code.visualstudio.com

71–80 of 247 posts

Re: How VSCode made bracket pair colorization faster (2021)

#71

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.

You didn't even bother reading the article, did you? The performance increase was achieved by inlining a third-party extension into VSCode itself.

Re: How VSCode made bracket pair colorization faster (2021)

#72
post #25

Earlier 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?

Just the standard Remote-SSH

https://code.visualstudio.com/docs/remote/ssh

Re: How VSCode made bracket pair colorization faster (2021)

#73

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.

I know reading the article is hard, but if you did you'd realize that it was slow because colorization was performed by an extension, and could not be optimized sufficiently because of limitations of the public API. They sped it up by moving it into the VS code core, which allowed it to take advantage of a bunch of features not available to extensions.

Re: How VSCode made bracket pair colorization faster (2021)

#75
post #8

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. 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.

Everyone should do a stint coding in vim, you learn so much about the things an IDE hides from you, and your terminal skills grow exponentially.

Re: How VSCode made bracket pair colorization faster (2021)

#76

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.

I mean, in this situation a big thing is taking a plugin and re-writing it as part of the core application. The initial plugin was inherently limited by the existing plugin API, which wasn't optimized for this specific use case.

"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)

#79
post #8

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. 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…

>> how incredibly fast desktop applications used to be decades ago

Are you still using that same computer from decades ago?

Re: How VSCode made bracket pair colorization faster (2021)

#80

Earlier 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.

I use vs code and jet brains intellij. Vscode is by miles more stable and light weight for running a java spring app. Of course intellij runs a lot of stuff but the experience is not better for it. Intellij feels like a sloth next to vscode
Post reply on HN