That’s what containers are for. Fucking up the container won’t fuck up the host. That was the best decision in self hosting I’ve done. Even that one virtual machine feels weird and uncomfortably legacy now but it needs to interact with hardware in a certain way that just won’t fully work with docker.

Python doesn’t have to. Windows supports both out of the box. Has been for many, many years

No. Because the python version of the host and the target server must loosely match up. Otherwise you get some cryptic error messages in some unexpected modules. Red Hat’s solution: just manage RHEL 9 targets from RHEL9 hosts and RHEL8 from RHEL8 hosts. There is no official way to align python versions across that major.

IBM owns Red Hat.

Blue Byte’s “Albion” https://en.m.wikipedia.org/wiki/Albion_(video_game)

My (self-hosted) cloud storage is larger than the disk drive on my laptop. On demand sync is important to me. I really, really hope Linux will catch up to Windows in that regard.

Currently we have an experimental VFS feature on all platforms that is using some suffix appended to files when they are virtual empty placeholders. https://github.com/nextcloud/desktop/issues/3668

Yeah, no thanks. It’s a very hacky work-around and breaks the moment you use an application that tries to access the files directly.

OS-level support for cloud storage. OneDrive, Dropbox and all the others work seamlessly on Windows through the Windows API. You can browse all the files on the file system and once you access them, the OS will call back the cloud provider to download them. It works through all applications, all cloud providers. I am aware that some tools on Linux have something similar to work around the issue in user land. Some solutions are less worse than others but none of them are as good as on Windows.

If you use something Android based for watching YouTube on the TV (some TVs, fireTV stick, etc.), you can: https://github.com/yuliskov/SmartTube?tab=readme-ov-file

I haven’t watched a single Ad on YouTube on TV (SmartTube), mobile (ReVanced), or PC (Firefox + uBlock origin) since it became unbearable… five years ago or so?

It’s visible in the PDF. I have used that extension to mark draft versions of documents. This makes it very obvious and saves you from accidentally handing in a draft. At least back when things were printed out much more often. With PDFs I find that the file name is sufficient.

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.

Postgres handles NoSQL better than many dedicated NoSQL database management systems. I kept telling another team to at least evaluate it for that purpose - but they knew better and now they are stuck with managing the MongoDB stack because they are the only ones that use it. Postgres is able to do everything they use out of the box. It just doesn’t sound as fancy and hip.

Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.