Eager Eagle

• i 👏 want 👏 emojis 👏 in 👏 my 👏terminal

github.com/ryanoasis/nerd-fonts

multi-line cursor gets close enough

I’m lazy, so I prefer to not remember what half a dozen cryptic flags stand for.

I just find disappointing that there’s no long form to these options and they don’t make much mnemonic sense either. Feels like the authors just picked the first letter available they came across with zero regard to readability or usability.

tbh they probably can, it’s just more ctrl involved

DeepSeek was built using older chips, but NVDA was priced on the premise that newer chips were almost a requirement for anyone seriously investing in machine learning.

Another factor was the open-sourcing of DeepSeek, which makes larger hardware investments harder to justify. Nvidia will continue selling, this is just a momentary stock price correction.

it’s still too high, it can fall much, much more

Can’t relate. I update compulsively every 2 hours on average.

#!/usr/bin/env python

After tens of thousands of bash lines written, I have to disagree. The article seems to argue against use of -e due to unpredictable behavior; while that might be true, I’ve found having it in my scripts is more helpful than not.

Bash is clunky. -euo pipefail is not a silver bullet but it does improve the reliability of most scripts. Expecting the writer to check the result of each command is both unrealistic and creates a lot of noise.

When using this error handling pattern, most lines aren’t even for handling them, they’re just there to bubble it up to the caller. That is a distraction when reading a piece of code, and a nuisense when writing it.

For the few times that I actually want to handle the error (not just pass it up), I’ll do the “or” check. But if the script should just fail, -e will do just fine.

oh the legendary December 2004 concert - I have a friend that was there

we need more hardworking people like that 💫🙏🏆