Docker's secret that most "getting started" tutorials seem to miss is docker-compose.yml. Who wants to type these long-ass commands to start containers? I always just create a compose file, and then docker compose up -d.
Dockerfile is for developers, you shouldn't need more than a docker-compose.yml for self-hosting stuff.
Well, someone did it at least partly: https://www.youtube.com/watch?v=zdPRhkbeQJk
Altough in this case it's to improve acceleration, not anything related to privacy.
Something something dining philosophers.
Oh, my sweet summer child...
From this thread, looks like you're right, sadly...
Even if Assange himself was openly interfering in US politics, how is that relevant? If he isn't a US person, and he's not on US soil, why would he be bound by US law? US law isn't universal law, you know.
Yes, but that's not treason. It could be treason if he was American, but he isn't.
I fail to see how that's relevant here. The guy isn't a US national and wasn't in the US when he committed his alleged "crime".
He has absolutely no duty towards the US and is 100% free to associate with whoever he wants, and yes, even Russia.
US has no standing whatsoever in this situation, and it's a travesty of international law that Sweden and the UK even entertained the idea of extraditing him. The response should've been "go sue the American who actually committed that crime on American soil. Oh wait, you've already convicted her, and she's already out after serving her sentence? WTF are you going on about then?"
It's true that you can easily fall into analysis paralysis when you start learning JS, but honestly things have somewhat stabilized in recent years. 10 years ago everybody was switching frameworks every 6 months, but these days we're going on 8+ years of absolute React dominance. So I guess that's it for the view layer.
The data layer has seen some movement in more recent years with Flux then GraphQL / Relay, but I think most people have settled on either Apollo or react-query now (depending on your backend).
On the backend there was basically only express.js, and I think it's still the king if you only want to write a backend.
Static websites came back in fashion with Jekyll and Github Pages so Gatsby solved that problem in js-land for a while, but nowadays Next also fulfills that niche, along with the more fullstack-oriented apps.
Svelte, Vue, Aurelia and Mithril are mostly niche frameworks. They have a dedicated, vocal fanbase (see the Svelte guy as sibling to your comment) but most of the industry has settled along the lines I've mentioned.
Honestly I think the main thing that the JS ecosystem does well is dependency / package management (npm). The standard library is very small so everything has to be added as a dependency in package.json, but it mostly works without any of the issues you often see in other languages.
Yeah, it's not perfect, but it's better than anything else I've tried:
In contrast, NPM is pretty simple: it creates a node_modules and puts everything there. No conflicts because project A uses left-pad 1.5 and project B uses left-pad 2.1. They can both have their own versions, thank you very much.
The only people who managed to mess this up are Linux distributions, who insist on putting things in folders owned by root.
C is crazy. While you are learning it you are learning Make and gcc without your consent.
Java is crazy. While you are learning Spring you are learning Maven or Gradle even without your consent.
Owner of 2 pinecils here, there are buttons and a display that shows the current temperature and other stuff. I only just learned that there's an app, it works more than fine on its own, out of the box.
I got that specific iron because I needed to power it from 12v, and it works very well on the USB PD power supply I already have for my laptop.