In that case I stand corrected on the whole orbit bit. Thanks for taking the time.
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 being 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.
It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?
This sounds an awful lot like victim blaming. It’s the responsibility of the museum to clearly communicate how the attraction should be used. For example by signage if it should only be used below a certain weight or age. There are plenty of examples of this with attractions elsewhere, so it’s not as if that’s remotely surprising or an undue burden or anything.
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)
No, I said they hadn’t demonstrated it. But 95% is close enough, I stand corrected.