641 karma · joined July 15, 2019
edit: to be clear, I'm taking about flakes, Guix does have plenty of mechanisms and utilities regarding direnv-esque project manifests, lockfiles, and even "inferiors" which let you install outdated packages that the distribution has otherwise moved on from by actually building and using the version of guix that the package would have been built with at the time
Other approachs to deployment in particular include the functional package managers Nix and Guix, which can create lightweight application images, and could probably be cobbled together into some sort of remote environment replication even across architectures. As I read on, I thought less about how this compares with Guix in regards to application/environment packaging and more about how these things could be glued together in interesting ways, because I think the intro leads in through slightly off-label examples, if that makes sense. Application packaging isn't what this addresses at the end of the day, but it's no less fascinating for it.
Previous discussion here: https://news.ycombinator.com/item?id=20455857
Also featured in that thread: https://github.com/akavel/up
For example: echo '' | fzf --print-query --preview 'grep -R {q} . 2> /dev/null'
For me programming was something that started gradually as I became familiar with Bash, until in denial that I was programming at all. Ansible introduced me to Python, Jinja, and YAML, but I still didn't consider what I did to be programming. Scripting, but "I'm no programmer", just in a sysadmin rabbit-hole. I'll have impostor syndrome real bad.
Going back to Bash after working with Python was rough, and I've since delighted in learning new programming languages and paradigms as I solve my problem-of-the-week, gaining a new understanding and appreciation of how people can approach programming each time. The problems are trivial in retrospect, but feel significant at the time- each is an important stepping stone in the broader understanding of computing that I'm developing, as well as an excuse to get sucked into the syntax, ecosystem, and mental model of a new perspective. Perhaps I'll learn to delight in C someday too, but today I've found my stay in Lisp, and look forward to using purer functional languages in the future.
A background, and the perspective it gives a person, is a unique and special thing.
"The US", however, means "The United States", which makes it really clear that you're talking about the States as a nation (or at least as organized states) and gives it a lot of resistance to this nuance. The cleanest equivalent would "America" vs "the Americas", but because that's clearly too broad. Where a single article is all it takes to change the implication in the case of Ukraine, here we'd need more explicitly refer to the land, like "the continental US territory".
It's also worth noting that no one would be scrutinizing statements about the US in the same way because it doesn't have a context that puts it in dispute. At least in casual contexts, inaccuracies are often overlooked when what you meant to say is clear and uncontroversial.
Not to mention accessibility features, which readers are well positioned to support.
Not to be too picky, these are my ideals and I wouldn't so blutly demand such feature coverage from a developer. Y'all do what you think is best and I'll find what works best for me, thx to amyone who's contributed to a reader c: