Earlier quoted context omitted.
Any interest in working together on a new extension?
What would be the possible solution ? Change size ? High contrast fg/Bg combinations ? Special UTF characters?
How VSCode made bracket pair colorization faster (2021)
21–30 of 247 posts
Re: How VSCode made bracket pair colorization faster (2021)
#22And yet, somehow, no one has done anything to address the inherent issues for colorblind developers. All of these colorization add-ons are woefully inadequate in that regard.
Seems like a fundamentally unsolvable problem. These techinques use a spectrum of colours for deeply nested brackets. (If you only have one or two levels of brackets then you don't need the colourisation in the first place.) But colourblind users fundamentally don't have that many choices of colours to pick from in the first place.
It isn't a complete replacement for bracket colorization, but it helps in a lot of cases.
(Not colorblind, I just prefer a grey scale theme for my indent reminders!)
Re: How VSCode made bracket pair colorization faster (2021)
#23Earlier quoted context omitted.
Any interest in working together on a new extension?
What would be the possible solution ? Change size ? High contrast fg/Bg combinations ? Special UTF characters?
Re: How VSCode made bracket pair colorization faster (2021)
#24If 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.
I'd say I never had issues with vscode performance and actually its performance is a major factor why I use it.
Re: How VSCode made bracket pair colorization faster (2021)
#25If 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.
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.
Re: How VSCode made bracket pair colorization faster (2021)
#26Re: How VSCode made bracket pair colorization faster (2021)
#27Just keep everything slow and then everything will be alright.
Re: How VSCode made bracket pair colorization faster (2021)
#28If 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.
Re: How VSCode made bracket pair colorization faster (2021)
#29If 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.
I do keep looking for lighter options, but have yet to find one that actually does all the things I want. Vim and emacs are okay, but getting the right plugins to get the right features I want is a pain. Other options seem to lack the ability to add those features at all.
Re: How VSCode made bracket pair colorization faster (2021)
#30If 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.
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.