I can't stand using VSCode so I wrote my own • Hacker News Board

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

#181

Post by lilbaby » Tue, Apr 23, 2024, 5:19 AM UTC

armchairhacker wrote: post #71

The author could try forking and patching VSCode to fix the annoyances manually. Years ago I had an issue with VSCode: it was missing a small feature that was very important to me, with the GitHub issue stuck in limbo. I ended up going into the source and implementing the feature myself. It took a few hours after bugfixing, I think the fix was ~100 LOC. Then I used the locally-built version. I recall building took a…

Had you been using Emacs you would have written the fix on-the-fly, eval it and have it be live without even restarting your editor :)

I check with VSCode regularly because obviously an editor that is used by that many developers is worth keeping tabs on (pun n.i.).

I spend some time with it and then go back to Emacs because I can’t justify the trade-off, giving up the raw power and performance for just being more in sync with my team or something.

I’ll readily admit some of the extensions are very nice, like stuff for Kubernetes and so on, and they work well out of box. On the flip side, the customization story is not so great.

With Emacs, I usually spend a bit of time with a new package learning how it works and customizing it to my liking and then it typically becomes more powerful and integrated in my workflow than the VSCode equivalent. Plus the LoC count of a package is usually far far less than of an VSCode extension and I can audit it much faster.

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

#182

Post by josephcsible » Tue, Apr 23, 2024, 5:16 PM UTC

wkat4242 wrote: post #131

0cf8612b2e1e wrote: post #105

Earlier quoted context omitted.

Clearly you do not work for corporate America. Any amount of performance loss is acceptable to check a security compliance checkbox somewhere.

Don't forget the enterprise market has a whole different threat model. Even though blanket exclusions are often used, a determined attacker will quickly figure out to dump their remote exploration tool in c:\dev .

If the attacker gets far enough to be able to put something in c:\dev and run it, your protections have already failed.

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

#183

Post by amne » Wed, Apr 24, 2024, 5:05 PM UTC

sibit wrote: post #139

Onawa wrote: post #102

Earlier quoted context omitted.

Microsoft has been flopping with their naming recently... Case in point, Copilot. GitHub Copilot, Microsoft Copilot, Office 365 Copilot... all different products for different uses. Still can't figure out why they didn't follow through with Cortana being the OS copilot name and retired it. It was such a perfect fit. My only guess is that they are worried about anthropomorphizing the AI.

> Still can't figure out why they didn't follow through with Cortana being the OS copilot name and retired it. I can't figure out why they didn't use it as an opportunity to bring back Clippy.

most likely because of greyhairs with PTSD

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

#184

Post by Vermyndax » Thu, Apr 25, 2024, 1:15 PM UTC

wg0 wrote: post #117

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.

It's the terrraform part of the LSP that's buggy and there's an issue open for that on Terraform extension's GitHub repo.

Yeah, the LSP does seem to go through some seriously bad days/weeks.

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

#185

Post by Vermyndax » Thu, Apr 25, 2024, 1:17 PM UTC

wffurr wrote: post #33

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.

Paper cuts like what? Deficiencies in the syntax plugins?

* Drag/drop support from Finder. * Git pre-commit chokes Sublime Merge (for some weird reason), I'm sure I can troubleshoot this but I every time I take a swing at it, it blows up in my face and I give up * Strange autocomplete issues * A few other things I forget about, but will try it again and see if I can remember

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

#186

Post by Vermyndax » Thu, Apr 25, 2024, 1:34 PM UTC

yjftsjthsd-h wrote: post #13

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.

> devops-y things (Terraform, OpenTofu, JSON, python, yaml, txt, dockerfiles, etc.) > I so, so wish there was a better way to do this without fucking electron. I do all of those things in vim and it works fine. No GUI and I'm sure it's missing some fancy new features, but it's fast and reliable (and it's not electron).

There is some syntax highlighting for Terraform in nano, so maybe I should try rolling with the terminal for a while.