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.

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.

Cool, thanks

It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?

Sure, there were electric cars. But if I remember correctly, Tesla was the first to deliver the whole next-gen package with an every day, everywhere car, plus charging stations plus the whole automation. If you wanted that, there was no way around Tesla for quite a while.

Teslas were the “best”, as in the only option for what they did. They were never the “best”, as in better than existing products for what they did.

Being first to market for such a long time was an incredible feat and it speaks volumes that their position isn’t much, much stronger at the end of it.

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.

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.

It’s the same argument. Getting a reasonable amount of charging is possible in 15 minutes. But not everyone has immediate access to fast charging stations. If everyone could always make a deliberate decision whether to go easy on the battery and save money or having to be places, EVs may look much more appealing to a lot of people.

It turns out there’s still plenty I don’t know, and I spend much more of my time confused and frustrated than I did before. The cool part is that I’m now confused and frustrated by really interesting problems.

This is spot on. Your whole response ist just a trove of insight, I wouldn’t have been able to articulate so eloquently.

Paperless -> Paperless-ng -> Paperless-ngx

Yeah, it’s the same for me. The content is awesome but requires a lot of concentration.

As you mentioned, with Fedora the best alternatives are immutable spins. Updating means downloading a new base image, applying overlays and additional installations to it and on the next reboot you start from that image. You can configure it to keep as many previous versions as you need and boot into those directly on startup. Since you never change your current image once it’s built, you can’t break a known good system. You can only ever break your next version and in that case, just boot the previous.

I’ve created an Ansible playbook that configures a vanilla Kinoite the way I want it. No need to back up the system if I can recreate it with less than a megabyte of text files. Secrets are in my password vault, personal files are in my personal cloud and get synced to and from the laptop continuously. I would never go back to backing up system files as opposed to recreating it with a playbook. That seems so wasteful in hindsight.

Flatpak with Fedora 39 must have come a long way. Almost every tutorial with workarounds or discussion of broken features you can find online is now obsolete. It just works out of the box, especially under KDE. Mostly. That makes searching for actual issues extremely hard because I find myself chasing down paths of issues that have long been resolved.