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

You Need to Ditch VS Code

jrswab.com

Post reply on HN
Print view View original

31–40 of 113 posts

Re: You Need to Ditch VS Code

#31

Post by monooso »

diarrhea wrote: post #25

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…

I agree that certain commands require some effort to learn, but I would not include `cp` or `mv` in that list.

Re: You Need to Ditch VS Code

#32

Post by PaulRobinson »

bhouston wrote: post #5

TL/DR: I strongly encourage you to understand the fundamentals and not view all of our tools as black boxes, but once you have an understanding of the tools and the various layers of abstraction, feel free to use them to boost your productivity and output. --- This is equivalent to saying "to understand wood working, do not use power tools, use hand tools to understand the wood and the process." Sure, if you want to…

Wrong way round.

git on the command line is the power tool. The VS Code plugin is the training wheels version.

These tools the TFA discuss are powerful, but have a learning curve. VS Code has a flatter learning curve, but it's up to you to decide if they are abstracting away things you actually need to understand.

All abstractions serve a purpose, but they're also always leaky. To extend your assembler analogy: sometimes you actually do need to understand what's happening on the stack and the heap, most people never do.

Use what works for you, but don't think that abstractions will be enough for every scenario, sometimes you're going to need to get under the hood and go deep, and if all you ever do is hand-wave it away and hope your IDE/framework/chosen programming language interpreter or compiler is going to just "sort it out" for you... well, good luck with that, and I hope it works out for you. It's just not my lived experience after 30+ years in the industry.

Re: You Need to Ditch VS Code

#34

Post by NooneAtAll3 »

no, we need to ditch *Javascript* in VS Code

IDE itself is good, "convenience" is benefit and not a sin - but performance and RAM usage needs to be better. And that is only done by throwing webstack into a dump

Re: You Need to Ditch VS Code

#35

Post by donkeybeer »

diarrhea wrote: post #25

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…

What is there to get wrong in your flattening dir example? I'd mv the internal dir as some other name to outside say dir2, them rm rf outer and mv the dir2. Unless there is something wrong in this approach.

I would agree with the rest, I always have to look up find and xargs syntax.

Re: You Need to Ditch VS Code

#36

Post by rounce »

imron wrote: post #16

> Try debugging without breakpoints Why would you need to give this up? I use breakpoints with terminal debuggers all the time.

It actually said

> Debug your code without visual breakpoints

With ‘visual’ being the important aspect.

Re: You Need to Ditch VS Code

#37

Post by nikanj »

robertjpayne wrote: post #18
imron wrote: post #16

> Try debugging without breakpoints Why would you need to give this up? I use breakpoints with terminal debuggers all the time.

Yea this take makes no sense. What in the world is wrong with debugging with breakpoints?

It’s a particular subcategory of cork sniffing where you pick the hardest, dumbest way to do things because you’re a Real Developer

Re: You Need to Ditch VS Code

#38

Post by jemmyw »

barishnamazov wrote: post #14

For me, the friction of VS Code is more cognitive than computational. I call it the "searching with your eyes" [0] problem. To make it clear, I've no problems with VSCode but haven't used it in a long time -- maybe it has added some keyboard-only features that makes workflow smoother. VS Code's heavy reliance on the file explorer tree forces you to constantly visually scan nested directories to navigate. When I switc…

VSCode doesn't heavily rely on the file explorer, that is personal preference. I use its jump to file far more than the explorer, both by filename, by reference jump and by "dumb" jump, a plugin that does simple reference jump with rg. That jump by reference just works now in VSCode for all the languages I use puts it ahead of neovim which requires a bit of fiddling to get going.

Re: You Need to Ditch VS Code

#39

Post by diarrhea »

barishnamazov wrote: post #14

For me, the friction of VS Code is more cognitive than computational. I call it the "searching with your eyes" [0] problem. To make it clear, I've no problems with VSCode but haven't used it in a long time -- maybe it has added some keyboard-only features that makes workflow smoother. VS Code's heavy reliance on the file explorer tree forces you to constantly visually scan nested directories to navigate. When I switc…

All IDEs including VSCode have fuzzy-finding for files, and fuzzy-finding for symbols as well. Between these, I never find myself using the file tree, except when it's the best tool for the job ("what other files are in this directory?", file tree manipulation (which IDEs recognize you doing, adjusting imports for you!) etc.).

I actually notice how this pattern is very fast, but I lose a code base's mental map. Coworkers might take longer to open any individual file but have a much better idea of repo layout as a whole. That makes them effective otherwise.

Re: You Need to Ditch VS Code

#40

Post by abhinai »

diarrhea wrote: post #25

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…

Most of the commands you've mentioned have worked fairly well for me. Are you sure you're looking up cp, mv and find every time before using them? Sounds pretty weird.
Post reply on HN