91–100 of 113 posts
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…
With fish, `for f in *.pdf` Just Works™.
Research on calculator use in early math education (notably the Hembree & Dessart meta-analysis of 79 studies) found that students given calculators performed better at math - including on paper-and-pencil tests without calculators. The hypothesis is that calculators handle computation, freeing cognitive bandwidth and time for problem-solving and conceptual understanding. Problem solving and higher level concepts mat…
> You're letting the IDE think for you instead of building a deep understanding…
That’s not specific to VS Code, you can say that about any IDE. The headline made me expect arguments specifically against VS Code. I want my 10 minutes back.
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…
With fish, `for f in *.pdf` Just Works™.
/s (I'm a big fan of fish)
Break your ankles with a hammer and start running, pain will build your character. That's about the level of advice I am getting from this article...
Ugh a terminal purist. Just as insufferable as the ones in person at work. Yeah have fun with your gigantic unorganized git diffs I guess.
I tried vscode and it just seemed like a crippled version of jetbrains, I don’t get it.
Earlier quoted context omitted.
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”.