GPS works without data or WiFi.
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
check this out
They run smaller variations of it in their personal machines. There are models that fit in almost any machine, but IME the first model that is useful is the 32b, which you can probably run on the XTX. Anything less than that, only for the more trivial tasks.
Can’t relate. I update compulsively every 2 hours on average.
the real malware is facebook
Nice, I’ve wanted something like this many times now.
hmm this gives me all colors (from ls and grep)
/usr/bin/ls -l --color=always | /usr/bin/grep --color=always a
(I’m using their full paths because I usually alias ls
and grep
to eza
and rg
respectively)
There’s a export CLICOLOR_FORCE=1
you can try to avoid repeating --color=always
, but that didn’t work for me with ls
and grep
specifically.
Edit: there’s also a FORCE_COLOR=1
that is popular, but again, neither ls
nor grep
seem to care.
Who’s setting up the system is not necessarily the same person using it.
besides just downloading and running a binary, there are plenty of package managers that work in the user space and don’t need root access.
I don’t https://xkcd.com/538/
I’m convinced the chances of me losing access to the data are higher than encryption protecting it from a bad actor.
Let’s be real, full disk encryption won’t protect a running system and if someone has physical access and really wants it, encryption won’t protect you from the $5 wrench either.
I do encrypt my phone data though, as someone running away with my phone is more realistic.
#!/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.
an actual print screen, finally
I don’t think I’ve used a screen saver in over a decade
that’s good if your data is not already compressed, otherwise is more of a CPU waste
images, videos, audio, game assets, standardized data files, and a bunch of other things are likely already compressed.
Same. And I was a Nova pro user years ago.