240 karma · joined June 7, 2013
for example, a computer system that routinely checks for updates will hopefully still function if the update server goes away. and you can always install another operating system.
since I listen to most music via a streaming service these days, I don't consider the music owned and don't mind moving to another service (which I have gone twice, losing playlists in the process).
the worst is "digital copies" of movies. I try not to buy these, but occasionally do. I'm pretty sure that Blu-rays I buy today will work until the media degrades, but have no such confidence in digital copies.
When the actual labor is done by part-timers with no health insurance making not much over minimum wage.
I'm still using my Pixel 6a and will probably continue until it fails or the battery life gets really bad.
I like keeping the rules of the language simple enough that there is never any confusion.
I have a soft spot in my heart for `pass` (http://www.passwordstore.org/), but it's a pain to access it from my phone.
If he wants to kill Twitter, that's fine by me. I prefer a more decentralized internet anyway.
sh 'make all'
sh 'make test'
In my `Jenkinsfile`, but there's not a great way to test things locally.For reading code, I tend to use `highlight -O xterm256 "$1"|less -R` or `source-highlight -f esc -o STDOUT -i "$1"|less -R` in a shell function.
if [ a = b ] || grep -q ^hello$ /usr/share/dict/words; then
echo "test failed and grep succeeded"
fi
> “You pick whether to be amused or horrified. I don’t know how exactly my coworker reacted when I hinted at this during a recent code review I did for them.”Isn't that normal everyday shell use?
I also really like writing software that builds HTML to be served as a static page. E.g. https://gist.github.com/HalCanary/61276afbab042e204e54268f6a... Then that complexity is hidden from the client.
(or that was true back when I worked on that code, two jobs back!)