Re:How VSCode made bracket pair colorization 10,000x faster
by bamfly on Thursday June 22, 2023 @12:08PM
(#36434338)
It's better than other Electron programs (a low bar, since most of those perform shockingly poorly) but eats way more system resources and performs noticeably worse than Sublime Text, on my machine.
[ Parent
| on HN ]
Re:How VSCode made bracket pair colorization 10,000x faster
by wiseowise on Thursday June 22, 2023 @02:18PM
(#36436465)
Oh noes, who could’ve thought that application written in JavaScript that gets executed on browser engine is slower than lean C++ that uses their own custom GUI toolkit
http://news.ycombinator.com/item?id=2822114.
Re:How VSCode made bracket pair colorization 10,000x faster
by VHRanger on Thursday June 22, 2023 @02:35PM
(#36436727)
Sublime text is an editor, VS Code is an IDE, though?
The featuresets aren't the same.
Re:How VSCode made bracket pair colorization 10,000x faster
by bamfly on Thursday June 22, 2023 @03:10PM
(#36437178)
I'd say they compete in a similar space of smart plugin-friendly code editor, not IDE.
What are you thinking of, in terms of differences? I use both quite a bit (some of VSCode's plugins are better) and have always viewed them as very close to one another, in terms of features.
Re:How VSCode made bracket pair colorization 10,000x faster
by tredre3 on Thursday June 22, 2023 @03:28PM
(#36437440)
For one thing VS Code has a full debugger with breakpoints and stack analysis that supports many backends out of the box, that's an IDE feature.
Sublime doesn't have any (real) debugger even with plugins. Some attempt to tack on a debugger but they have to do so via popup menus or overloaded "magical" text buffers and it's atrocious. Why can't I click on the line I want to break on? Why can't I see the stack in a nice editable tree? Right, because sublime is a text editor and VS Code is an IDE.
Re:How VSCode made bracket pair colorization 10,000x faster
by bamfly on Thursday June 22, 2023 @03:43PM
(#36437673)
Ah—I'd never noticed VSCode could do that, in years of using it. I ignore some of its features (some of which Sublime also has, and I tend to ignore them there, too) because I find them janky and fragile or requiring-configuration such that I lose a lot of time keeping them happy, like any kind of run-from-editor stuff and the built-in terminal (it always seems to have a messed-up environment or get itself into broken states) dropping to a separate terminal for that sort of thing. Not like when I'm, say, working in XCode or Intellij and almost exclusively run, build, & debug from inside the IDE, rarely touching a separate terminal.
Guess you've got a point, then, and I just don't use it that way.