TIL, thanks!
This (and systemd bugs) is the main reason I moved away from nixos on my homeserver. Nowadays if I want declarative configuration, I just cram everything into docker containers and write a huge docker-compose.yml
for everything that I want to run. Would still recommend nixos for things that don't require a lot of tweaking. Like if I had to set up a simple website for a small business or something. I love how you can set up SSL certificates for nginx with autorenewal just by switching it on in configuration.nix
.
Ususally just turning off javascript using ublock makes these notices go away. And if turning off javascript breaks the website... well then I guess whatever I was trying to read wasn't really worth my time anyway.
Void on laptop, alpine on homeserver. Yep, checks out.
Love how the indian guy sitting meme perfectly sums up how I feel about alpine, nixos, and freebsd, even though those are completely different projects with different directions and goals. "It's boring and it just works".
Yay!
Tangentially related, but I love how http://ai is an actual website that you can visit. We're so used to thinking of websites as <something>.<tld>
that it's really weird to see a website hosted directly on a top level domain with no subdomain.
John Oliver did a nice explanation
Basically they pretend to have the wrong number, but then start chatting with you, gain your trust over a period of months, and then ask you for money or similar.
So...
- normal people are scared because they fall for the gambler's fallacy,
- mathematician is feeling fine because a 50% chance is a 50% chance,
- and the scientist is feeling extra fine because the experimental data shows that the surgery is actually safer than 50%
Did I get it right?
Okay, then that means I misunderstood your comment. Seems like we're on the same page.
Funny you say that lol. I study electrical engineering, and my friends from uni ABSOLUTELY talk about linux, self hosting, and privacy. Still looking for someone to fill out the "bad thing that amazon did today" conversation niche.
Maybe I'm confused, but from what I understand, "declarative" means you tell the computer what you want the final thing to look like, and "imperative" means you tell the computer what steps to take. So Dockerfile would be imperative because it's a set of commands that are executed in-order to create the image. Meanwhile docker-compose.yml is declarative because you say which containers are used with what options and how they're interconnected. IDK tho, as far as I understand the definitions aren't that rigid