That’s not the case (at least in Germany). Being brain dead does not replace the conscious decision on when to disable life support.

No, I said they hadn’t demonstrated it. But 95% is close enough, I stand corrected.

In that case I stand corrected on the whole orbit bit. Thanks for taking the time.

I didn’t say “a little” money. It may be important or critical for the business but from a technical perspective, demonstrating how it can safely bring loads up and down decides whether the whole concept is actually feasible. That’s when people will start to get excited.

As far as I understood it, SpaceX uses the word “orbit” liberally. If it reaches the hight where an orbit would be possible, that’s “being in orbit” for them. In an actual orbit, the rocket would not fall back down again in an hour or so without active breaking. If my understanding is incorrect, I’m happy to be corrected. And even of that was achieved soon, it’s still all without demonstrating that the starship could actually carry a load and return it safely. Not even an inexpensive dummy load. All SpaceX is showing in their live feeds are empty cargo holds that fill up with hot gases and fumes during reentry.

I think the average person gets it right. It’s a nice feat to catch the booster and it will save money. But that’s a side quest. The main quest of getting an actual load to orbit and beyond is still pretty far away. At least compared with the official time line where they wanted to achieve much more than that three years ago.

Termination without notice in Germany? That’s a major challenge even in situations that warrant it.

Ansible playbook is perfect for this. All your configuration is repeatable, whether on a running system or a new one. Plus you can start with a completely fresh newest version image and apply from there, instead of starting from a soon-to-be outdated custom image.

I specifically picked the statistic that claimed to have included the full cost of installing something new. Most other statistics only include prolonging the life of existing plants, thus ignoring the installation costs completely. You can just quote the paragraphs that prove your point the same way I have and then we can discuss further. Maybe I made a mistake, who knows.

Extremely cheap per kilowatt? Every statistic out there that I’ve seen and that includes government funding, as well as construction and deconstruction costs, paints a different picture. Nuclear is only competitive with coal or the relatively underdeveloped solar thermal.

In 2017 the US EIA published figures for the average levelized costs per unit of output (LCOE) for generating technologies to be brought online in 2022, as modelled for its Annual Energy Outlook. These show: advanced nuclear, 9.9 ¢/kWh; natural gas, 5.7-10.9 ¢/kWh (depending on technology); and coal with 90% carbon sequestration, 12.3 ¢/kWh (rising to 14 ¢/kWh at 30%). Among the non-dispatchable technologies, LCOE estimates vary widely: wind onshore, 5.2 ¢/kWh; solar PV, 6.7 ¢/kWh; offshore wind, 14.6 ¢/kWh; and solar thermal, 18.4 ¢/kWh.

Emphasis mine, source: https://world-nuclear.org/information-library/economic-aspects/economics-of-nuclear-power

Modern browsers happily show you the actual characters, while sending their encoded entities to the server. So, from a user perspective there is no ASCII limitation. Case in point: söhne.at (just some random website, I have no idea what they are or if they are legitimate)

1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/

Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.

When I installed Kinoite to start using Linux as my primary daily driver, the first thing I did was setting up Ansible, creating a new playbook and all Linux configurations I made from that point on, are only ever done through that playbook, which is backed up in my Forgejo instance. One command and everything is being set up exactly the way I want. It feels extremely liberating.

Windows hss supported slashes in both directions for a very long time. I almost exclusively use forward slashes to reduce mental load when switching between OSes.

Very well written. I’d only change something about this paragraph:

• Operated without production interruption even with frequent team member exit during critical phases of operation

Sounds like people were quitting on you because of terrible work conditions you fostered. An alternative could be:

• Operated without production interruption even with occasional unexpected or planned team member absences during critical phases of operation

The original author of git flow begs to differ. But hindsight is always 20/20 https://nvie.com/posts/a-successful-git-branching-model/

If you use feature flags, don’t forget to remove them after some grace period. Almost everything bad about feature flags that you can read online is related to long-lived feature flags and all the dead code and complexity involved. Adding a feature flags without a commitment and plan to remove them (the flag, not the feature), is asking for trouble down the line.

It depends. Some hardware degrades gracefully while my current desktop system won’t even boot and throws error codes on an empty battery. It took me hours to figure out what was wrong the first time it happened.

Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.