2 ms·

> I don't know why you're saying they are slow Because the slowness, when compared to a whole slate of "regular" (== non-web-browser-based) editors, is empiric

by veidr 10y ago

> I don't know why you're saying they are slow Because the slowness, when compared to a whole slate of "regular" (== non-web-browser-based) editors, is empirically measurable, and is not just like "twice as slow" or "500% less efficient", but — in many cases, for various operations, as most recently delineated by the joe's own editor benchmarks, but really I mean repeatedly demonstrated over and over for the life of these editors — hundreds of times slower or even infinitely slower (it just gives up and crashes). To a lot of people, that's infuckinsanebro!!!, like a car that gets not n miles per gallon, but needs n gallons per mile. I get that the extensibility and hackability is appealing. I like that, too. But at what cost!

itake 10y ago
have you used VS code? I recently switched from Sublime to VS Code. Originally, I hated the slowness. But the slow point in my work (Software engineer) is not how fast I open files, but on how easy is it for me to transfer what I am thinking to the screen. VS Code, while slow, has extensions that make me much more productive than when I was using Sublime. Highlights include: - auto-formatting my ruby code to fit coding standards. I don't have to spend time mucking with spacing. I write it the fastest way I can, and it fixes it. - inline git blame. I can easily see who and why a line of code is changed as I select each line. Super useful when debugging. I don't have to kick up the console or fire up github.com in my browser. - prettify json. I don't have to open up chrome to some json formatting tool to debug my http responses. edit: I still have to use sublime to open very large files, but that is rare in my work.
- veidr 10y ago
  Yeah, I have, and I actually use it regularly (along with several other editors). The slowness (of not just opening files, but editing them) drives me up the wall, but in certain workflows (e.g., TypeScript) it can be worth it.

by veidr 10y ago

itake 10y ago

have you used VS code? I recently switched from Sublime to VS Code. Originally, I hated the slowness. But the slow point in my work (Software engineer) is not how fast I open files, but on how easy is it for me to transfer what I am thinking to the screen. VS Code, while slow, has extensions that make me much more productive than when I was using Sublime. Highlights include: - auto-formatting my ruby code to fit coding standards. I don't have to spend time mucking with spacing. I write it the fastest way I can, and it fixes it. - inline git blame. I can easily see who and why a line of code is changed as I select each line. Super useful when debugging. I don't have to kick up the console or fire up github.com in my browser. - prettify json. I don't have to open up chrome to some json formatting tool to debug my http responses. edit: I still have to use sublime to open very large files, but that is rare in my work.

veidr 10y ago
Yeah, I have, and I actually use it regularly (along with several other editors). The slowness (of not just opening files, but editing them) drives me up the wall, but in certain workflows (e.g., TypeScript) it can be worth it.