Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

I can't stand using VSCode so I wrote my own

bold-edit.com

Post reply on HN
Print view View original

51–60 of 186 posts

Re: I can't stand using VSCode so I wrote my own

#51

Post by Scarbutt »

INTPenis wrote: post #30
Vermyndax wrote: post #4

I use vscode for doing devops-y things (Terraform, OpenTofu, JSON, python, yaml, txt, dockerfiles, etc.) and sometimes the way it bogs down my system drives me bananas. I'll punt to Sublime Text on occasion and use it for a few days, but then start running into papercuts in various places and have to go back to vscode. I so, so wish there was a better way to do this without fucking electron.

Makes me glad I stuck with vim. I do pretty much the same thing as you, what made you use vscode in the first place? What are the coolest features in your context?

IMO, the big is one good/smart programming language support, either out of the box or with a few clicks. If you know vim well, the vim plugin has serious limitations though. On windows/linux the reliance on home/end/pgup/pgdn/arrow-keys/del/mouse etc... is atrocious if you are used to vim so the vim plugin is still a life saver. The remote dev extensions also pretty good.

Re: I can't stand using VSCode so I wrote my own

#52

Post by [deleted] »

cyanydeez wrote: post #39
scoopdewoop wrote: post #32

Earlier quoted context omitted.

Why do you think your issue has anything to do with electron? That sounds like a meme. It is your drives, no? Does the browser make your system drives work a bunch? Much more likely, it is VSCode running ripgrep (rg in htop/activity monitor) in the background to find symbols in your codebase. That would be exactly the same regardless of GUI toolkit. edit: misread "system drives me bananas" as pertaining to "system dr…

Its not electron, but abusing the webview rendering for realtime software'

[deleted]

Re: I can't stand using VSCode so I wrote my own

#53

Post by cjensen »

kcplate wrote: post #48
macromaniac wrote: post #42

>I'd tweak the script; then to see the results I would press F5 to run the already built binary and wait over a second EVERY SINGLE TIME (about 1480ms). I put in a bug report for this years ago but it got ignored :( https://github.com/microsoft/vscode/issues/137066 Vscode has gotten slower over time. It's true you can't get nanosecond performance out of JS, but anything under 17ms should be trivial. I believe the vsc…

Everybody who worked writing code in the 70s-90s is smirking at “wait over a second”. Back in the day, I used to go get my coffee, shoot the shit in the break room for a few minute, and come back to find my debug runs just starting.

Turbo Pascal was so fast in the 80s that if I saw a syntax error further down the page it was faster to hit "compile" and let the compiler move the cursor to the error than it was for me to move the cursor myself.

It was a very special compiler and they don't make them like that anymore.

Re: I can't stand using VSCode so I wrote my own

#54

Post by outside1234 »

cjensen wrote: post #53
kcplate wrote: post #48

Earlier quoted context omitted.

Everybody who worked writing code in the 70s-90s is smirking at “wait over a second”. Back in the day, I used to go get my coffee, shoot the shit in the break room for a few minute, and come back to find my debug runs just starting.

Turbo Pascal was so fast in the 80s that if I saw a syntax error further down the page it was faster to hit "compile" and let the compiler move the cursor to the error than it was for me to move the cursor myself. It was a very special compiler and they don't make them like that anymore.

It’s crazy that this is still the gold standard

Re: I can't stand using VSCode so I wrote my own

#55

Post by doix »

kcplate wrote: post #48
macromaniac wrote: post #42

>I'd tweak the script; then to see the results I would press F5 to run the already built binary and wait over a second EVERY SINGLE TIME (about 1480ms). I put in a bug report for this years ago but it got ignored :( https://github.com/microsoft/vscode/issues/137066 Vscode has gotten slower over time. It's true you can't get nanosecond performance out of JS, but anything under 17ms should be trivial. I believe the vsc…

Everybody who worked writing code in the 70s-90s is smirking at “wait over a second”. Back in the day, I used to go get my coffee, shoot the shit in the break room for a few minute, and come back to find my debug runs just starting.

And in the 00's things were pretty instantaneous, at least from a UI perspective. I actually developed some "bad" habits where I'd just hold the step hotkey down to advance my program when debugging. And everything just worked and was synchronous. All the registers updated with each step, as well as my watched variables and everything else I can think of. I'm pretty sure this was visual studio 6.

That was peak Microsoft debugging experience for me, everything after that was worse, admittedly I did drop it and moved to Linux, so maybe it is good now. Although I very strongly doubt it.

Re: I can't stand using VSCode so I wrote my own

#56

Post by cjbgkagh »

macromaniac wrote: post #42

>I'd tweak the script; then to see the results I would press F5 to run the already built binary and wait over a second EVERY SINGLE TIME (about 1480ms). I put in a bug report for this years ago but it got ignored :( https://github.com/microsoft/vscode/issues/137066 Vscode has gotten slower over time. It's true you can't get nanosecond performance out of JS, but anything under 17ms should be trivial. I believe the vsc…

Wow, marked as-designed. I guess that's one way to fix the issue. In my experience latency needs to be < 250ms to be considered good, 500ms is roughly the max people can put up with, 2s is enough to drive people insane.

Re: I can't stand using VSCode so I wrote my own

#57

Post by awfulneutral »

causal wrote: post #18

BTW if VSCode is slow for you, check what extensions you have installed.

Yeah, for me it's more than fast enough except for the Microsoft pylance and C# extensions, both of which I really need to feel productive, and both of which (especially pylance) make VS Code much slower and buggier. It has been getting bad enough that I've been looking around for other editors, but as far as I can tell VS Code really wins on having all the language features, plus copilot and git integration in a single place.

Re: I can't stand using VSCode so I wrote my own

#59

Post by bigcoke »

gostsamo wrote: post #22

VSCode is still on the top of accessibility, so when you can claim that you work perfectly with a screen reader, you will convince me to switch.

people often overlook accessibility and other essential features of a modern editor, you telling me that your rudimentary rust editor is faster than vscode? and? people don't use it because it's fast (it's not).

Re: I can't stand using VSCode so I wrote my own

#60

Post by vbezhenar »

cjensen wrote: post #53
kcplate wrote: post #48

Earlier quoted context omitted.

Everybody who worked writing code in the 70s-90s is smirking at “wait over a second”. Back in the day, I used to go get my coffee, shoot the shit in the break room for a few minute, and come back to find my debug runs just starting.

Turbo Pascal was so fast in the 80s that if I saw a syntax error further down the page it was faster to hit "compile" and let the compiler move the cursor to the error than it was for me to move the cursor myself. It was a very special compiler and they don't make them like that anymore.

The trick is to have language "optimized for compilation" and do not do fancy optimizations.

Java is similar (but overall infrastructure around compiler makes it slow).

Golang also quite fast.

Post reply on HN