This change would also be bad for anything that scans for keywords, which includes most applicant tracking software.
This change would also be bad for anything that scans for keywords, which includes most applicant tracking software.
Rust: “Oh honey you aren’t ready to compile that yet”
Other people: Hmm I only use a few commands on this thing, I wonder if I can just refer to them by number or something?
You: Googling African tongue-snapping languages
“That sign can’t stop me because I can’t read!”
YMMV. I know it’s a good step down for some folks, especially as you can get carts with decreasing levels of nicotine. But in my case, the accessibility of vaping (which I did inside and in smaller more frequent doses, unlike how I smoked) set me back a bit and I felt like I started quitting all over again.
So, only about a decade until reaching feature parity with something like lazygit?
Interesting project but this write-up has a bizarre focus on number of lines of code, which doesn’t appear to differ substantially between the two approaches.
RE your edit: I also support that conclusion and I’m glad you’ll give it a shot yourself. A mindset that helps me is this: commenting is part of the iterative code writing process. When I’m struggling to put a concise and understandable comment above some code, it almost universally means that there’s something about the code itself I should arrange more clearly. This is your chance to do some rubber ducking, it’s valuable to both you and the next person to read your code!
Yes, join us!
Removed by mod
Going by what I use the most: Firefox, git, less, tailscale, midnight commander
I will never use a terminal that requires a subscription to use my own damn computer.
deleted by creator