Live data from Hacker News

You Need to Ditch VS Code

jrswab.com

111–113 of 113 posts

Re: You Need to Ditch VS Code

#111

"You should not let your IDE do the thinking for you" As a solo entrepreneur, if something enables me to execute faster, I'll gladly use it. Articles like this only remind me to never (again) hire expensive, pedantic, over-principled and cynical engineers.

Some of the older heads here are 100% with you, the notes and comments in this thread should be clear enough indication of that.

But you're right, tools that make short work of ridiculous incantations, 100% good.

We don't sit around trying to re-write arithmetic, but apparently not knowing how to do git pull --rebase is a crime to these smart folks, who don't seem to realize they know very little about getting sh!t done.

Re: You Need to Ditch VS Code

#112

No thank you... One of the primary things shells are supposed to excel at is file system navigation and manipulation, but the experience is horrible. I can never get `cp`, `rsync`, `mv`, `find` right without looking them up, despite trying to learn. It's way too easy to mess up irreversibly and destructively. One example is flattening a directory. You accidentally git-cloned one too deep, into `some/dir/dir/` and wan…

can never get `cp`, `rsync`, `mv`, `find` right without looking them up Wow! You have the brain really fried by not using it if you have issue using these simple command without help. I would double down on advising you to go back learning to use the roots before getting IDE or llm assistant...

Interesting attack on my person!

The things I want to get done on my computer are so much richer than moving files back and forth in a terminal all day. Simple things should be simple. Tools should enable us. Moving files is a means to an end and these commands having so many sharp edges makes me unhappy indeed.

But yes, of course I am an IDE toddler and cannot even tie my shoes without help from an LLM, thanks for reminding me.

Re: You Need to Ditch VS Code

#113

Earlier quoted context omitted.

VSCode over SSH kinda rocks honestly. I use it with my server all the time.

In my previous work, a few folks in my team used VSCode on a shared dev box. The box has 1TB memory, and we'd frequently OOM due to vscode servers taking up tens of GBs of memory (which adds up quickly when there are multiple vscode windows per person). Sometimes it'd eat as big as 100GB until it had to be restarted. Sure, big codebases, but that's just straight unacceptable.

I mean I've used code over SSH on machines that won't even have ten gigs of RAM let alone tens of gigs. I use it via WSL at work on huge projects but WSL might have optimizations plain SSH doesn't. Idk what y'all are doing, that sounds like you've done something strange.
Post reply on HN