How VSCode made bracket pair colorization faster (2021) • Hacker News Board

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

#231

Post by reaperducer » Fri, Jun 23, 2023, 2:06 AM UTC

IceSentry wrote: post #228

reaperducer wrote: post #68

Earlier quoted context omitted.

VSCode is a good tool, but it’s unbearably slow The funny thing is that the reason I and many other people switched to VSCode is that it used to be so speedy. I sometimes wonder how much of its decrease in speed over the last few years is due to feature bloat (which it seems to have in spades) and relying on hobbyists, who have less incentive to optimize, to fill out the plug-in ecosystem. I moved my personal project…

If vscode slowed down for you it might mean you installed too many extensions. Personally it feels just as fast or faster than before. Especially with things like the mentioned bracket colorizer beinf built in compared to the extension I was previously using.

As I stated, I have four plug-ins.

If VSCode can't handle four plug-ins, it isn't fit for purpose.

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

#232

Post by jcparkyn » Fri, Jun 23, 2023, 2:22 AM UTC

nielsbot wrote: post #198

One thing I miss the most from Xcode is the ability to double-click on any delimiter pair ([...], (...), , {...}) to select all text between those delimiters. I filed an issue against VSCode to get this implemented, but it never got enough upvotes.. Maybe posting about it here is my chance to get it done? :-P https://github.com/microsoft/vscode/issues/85587

Not quite what you're asking for, but you can click after the first bracket and then use the "Go to bracket" command to get roughly the same thing. You'll have to add a keybind for it though, there isn't one by default.

For slightly more control, you can also use alt+shift+right (or left) to expand/contract your selection to the matching bracket.

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

#233

Post by rochak » Fri, Jun 23, 2023, 2:43 AM UTC

Narishma wrote: post #74

Do people really like this type of syntax highlighting? The screenshots in the article to me are a hard to read color soup.

I agree. That’s a bit much.

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

#234

Post by chii » Fri, Jun 23, 2023, 2:56 AM UTC

grog454 wrote: post #150

Solvency wrote: post #15

Earlier quoted context omitted.

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…

Some people can't tell the difference between 17 ms of latency and 68 (4 frames at 60hz), while some can't bear it.

unless one is playing e-sports with vscode, i dont think a latency of less than 100ms is something to worry about at all.

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

#235

Post by pmarreck » Fri, Jun 23, 2023, 3:50 AM UTC

dmonitor wrote: post #56

pmarreck wrote: post #20

Earlier quoted context omitted.

It's not unsolvable. Colorblind people are missing one axis of color (such as the red-green axis). It is perfectly mathematically possible to pick colors that do not only differentiate along this axis, hence this option in many AAA games. Here's an online simulator to see what colorblind people of various types see. Note that if you yourself try this and the colors for one of the examples don't seem to change from th…

just the ability to change the bracket colors with reasonable default selections for colorblindness seems like a more than reasonable request

I’m not colorblind but I would wholeheartedly agree because I know colorblind guys

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

#236

Post by 5e92cb50239222b » Fri, Jun 23, 2023, 5:21 AM UTC

whynotminot wrote: post #199

5e92cb50239222b wrote: post #194

Earlier quoted context omitted.

Or maybe you're just fine with throwing away thousands of dollars at it every few years, so you're not seeing the problem. The "solution" that most of the world simply cannot afford.

If I could roll my eyes any harder, they’d be spinning. 99.9% of people who complain about electron apps are not ardent defenders of third world computing. It just violates their sensibilities.

I am not one of those "99.9%" (seems like a random number pulled out of someone's ass). Most developers in my poor country don't make much and would quality as lower-middle class in yours. Including a good friend of mine, who is learning web development on a 10-year old laptop — he can't afford anything else. I know he struggles with VSC because I hear about it daily.

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

#237

Post by 5e92cb50239222b » Fri, Jun 23, 2023, 5:22 AM UTC

wiseowise wrote: post #197

5e92cb50239222b wrote: post #194

Earlier quoted context omitted.

Or maybe you're just fine with throwing away thousands of dollars at it every few years, so you're not seeing the problem. The "solution" that most of the world simply cannot afford.

Of cut it off with most of the world bullshit, we’re talking about development tool here, not solving world hunger.

There are no developers outside Silicon Valley, got it.

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

#238

Post by 5e92cb50239222b » Fri, Jun 23, 2023, 5:25 AM UTC

akkad33 wrote: post #218

5e92cb50239222b wrote: post #191

Earlier quoted context omitted.

It also does maybe a quarter of what IDEA can do. Let's see how it performs when it catches up to what IDEA does right now (maybe in another ten years).

It does everything I need to run to do my job. If intellij is doing more stuff that is slowing it down then maybe they can find a better performance-feature trade off by getting rid of the bloat

It would turn into another run of the mill text editor like VSCode then, and would lose most of its users.

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

#239

Post by wiseowise » Fri, Jun 23, 2023, 6:00 AM UTC

5e92cb50239222b wrote: post #237

wiseowise wrote: post #197

Earlier quoted context omitted.

Of cut it off with most of the world bullshit, we’re talking about development tool here, not solving world hunger.

There are no developers outside Silicon Valley, got it.

Right, because world is divided in Silicon Valley and third world hellholes.

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

#240

Post by IceSentry » Fri, Jun 23, 2023, 7:55 AM UTC

xigoi wrote: post #172

IceSentry wrote: post #169

Earlier quoted context omitted.

I use discord and gitkraken every day and I've never had any issues either. People just like to complain. They act as if using a few hundred megabytes for the main app you are using is an issue. It's not the 90s anymore ram is cheap, especially at those amount.

Why is it better to have a million people buy more RAM, creating a large amount of electronic waste and emissions, instead of putting some effort into not unnecessarily wasting resources?

You don't need to buy more ram. It was already cheap a decade ago. Ram has been in the multiple gigabyte range for longer than that. Having an app that you use all the time every day use a few hundred of the otherwise unused ram is perfectly reasonable.