> Try debugging without breakpoints Why would you need to give this up? I use breakpoints with terminal debuggers all the time.
Tbh it's the default way I start my app in, debug mode xD
You Need to Ditch VS Code
41–50 of 113 posts
Re: You Need to Ditch VS Code
#42Ugh a terminal purist. Just as insufferable as the ones in person at work. Yeah have fun with your gigantic unorganized git diffs I guess.
You can clean up git diffs a lot, I personally find them easy to ready anyway, with tools like delta[1] which make things super nice to read. Also if you use a text editor such as neovim you can integrate these things into your editor and get beautiful diffs right there. That said I do not use neovim or delta, I just use git diffs or my language ide's diff features. [1]: https://github.com/dandavison/delta
> I personally find them easy to ready anyway, with tools like delta[1] which make things super nice to read. Also if you use a text editor such as neovim you can integrate these things into your editor and get beautiful diffs right there.
All I can see here is “if I use two extra tools, I can almost have as good an experience as vscode (or IntelliJ or whatever) gives me out of the box”.
Re: You Need to Ditch VS Code
#43No 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…
With fish, `for f in *.pdf` Just Works™.
Re: You Need to Ditch VS Code
#44For 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…
Don’t you just press ctrl p and type in vscode?
That exists, though it doesn't have a preview of the file. Also, jump lists to quickly take a look and ctrl+o to go back is a huge game changer for me. Not sure if VSCode supports that now, haven't used it in a long time.
Re: You Need to Ditch VS Code
#45> This deeper understanding makes you a more capable programmer because you know exactly what's happening under the hood. No. > In these situations, your VS Code knowledge won't help you. https://code.visualstudio.com/docs/remote/ssh > When VS Code formats your code, you don't learn your language's style conventions Lmao, what is this argument. `go format`, `prettier`, `ktfmt`, `ruff|black` is what you should know, n…
I don't necessarily agree with your thrift store take, I understand making a great personalised ide with vim or emacs. But I do agree with you that all the other points make no sense. VSCode doesn't solve your merges for you any more than vim does, the resolve tooling is very similar. VSCode doesn't do the build for you either.
Re: You Need to Ditch VS Code
#46> 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 is for many problems, especially concurrency related ones, much less powerful than trace points. But the issue I have seen is that some tools like gdb have unergonomic support for tracing so there I tend to use break points or printf debugging just because the tracing support is so bad in gdb.
Re: You Need to Ditch VS Code
#47This argument that “convenience makes you weak” can be taken all the way to “real programmers write assembly” or “binary is the one true path”.
On the other end it’s also “I’ll vibe code it bruh”.
So we land at the eternally wise YMMV.
Re: You Need to Ditch VS Code
#48Earlier quoted context omitted.
Don’t you just press ctrl p and type in vscode?
That exists, though it doesn't have a preview of the file. Also, jump lists to quickly take a look and ctrl+o to go back is a huge game changer for me. Not sure if VSCode supports that now, haven't used it in a long time.
It has jump previews and yea ctrl+o works
Re: You Need to Ditch VS Code
#49Earlier quoted context omitted.
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.
Which language/plugins?
C++ (clangd) and Python (pyright and ruff). But I think the excessive memory usage came from huge number of files in the code base, plus some really large files (given I ran LSP on neovim too with much smaller footprints).
Re: You Need to Ditch VS Code
#50Is the author aware of the vim plugin?
Every VSCode (Neo)Vim plugin I’ve tried (most, if not all of them) is a janky mess of random missing features and/or broken state handling. They’ve all felt like a worse experience than just doing things the ‘normal’ VSCode way.