It probably would have been less bad if he had chosen MPL-2.0 or LGPL-2.1-or-later. But he chose MIT, which cuts at the core of the intent of licensing the project with a share-alike license.
And for comparison, today you can do an economy round-trip flight with Delta Air Lines for roughly $1.6k (SEA-HND). A Delta One flight is roughly $8.5k. That's the apples-to-apples comparison.
Deregulation also allowed international carriers to sell to us too. An ANA round-trip on economy class is a couple hundred dollars cheaper. Their business class is similarly cheaper than Delta One.
Air travel is so much cheaper than it was back then that it is affordable for most people to take one international trip a year if they really want to. Even to exotic places in Asia or Southern Europe.
The interstate system only succeeded because the federal government took the very rare step of steamrolling all the states and individual landowners. It was done in service of putting people to work and stimulating the economy. But it was not a well-liked project.
Today, it is well-regarded, but when it was being done? No way.
It's rarely that simple. The question has to be asked "who owns the land?" because usually the rail lines get to belong to who owns the land, even if someone else builds them.
The interstate automobile road system got built through judicious use of eminent domain. That avoided all of these issues. Amtrak doesn't have the ability to do that.
Apple doesn't make regional variants of the phone, so all models have the technology built-in, even if it's disabled by default. Android phones outside of Japan lack Suica support.
The question to ask is "who owns the rail lines?". That matters for having a good rail system. It's basically the same problem for why the US doesn't have fiber internet available everywhere, too.
China also has nationalized rail systems. The major reason for the failure in the US is that the rail lines are not publicly owned. The reason the rail systems never got upgraded and Amtrak couldn't deploy high speed rail everywhere (despite it being a national priority in the 70s, 80s, and 90s) is that outside of the northeast corridor, Amtrak doesn't own the lines and couldn't get the owners to allow Amtrak to upgrade them for passenger high speed rail.
Yes, that is true, but in practice nobody has ever done that. And the material complexity of offering that mode is higher than just dynamically linking the library.
Also, modern compilers make this method much harder to use. It is much harder to stably relink object files like that than to just use the normal dynamic link method.
> Edit: Some comments mention Qt which could also work although how large is the runtime? Can it be compiled statically?
You need a commercial license for that, but yes you could. But since applications are typically distributed with install bundles that put into application-local program files directories, it's not super-important as long as you only cherry-pick the Qt libraries you need.
It's pretty much rpm-ostree. Nobody bothered to make those workflows performant, so if you need to apply updates separately, it's going to suck. The OSTree download can be fast if you have a fast connection to the Fedora server, but it's not mirrored and there's no mirror network support (so no geographically close downloads). To be fair, bootc has this problem too because container tooling in general can't support mirror networks currently.
I think it's also worth noting that the Dockerfile format is still driven by Docker, and there have been zero extensions to the format by Podman folks, so Containerfile==Dockerfile.
Microsoft has effectively ended support for the self-hosted versions of the groupware stack. So between Microsoft and Google (since both are SaaS), I would pick Google. Especially as I've had to administer both solutions before, and I would never voluntarily choose Microsoft 365 ever again.
And yes, you can regularly export your data out of Google Workspace and there are tools that can process that data and use it easily enough.
SUSE used Teams for years (particularly under Melissa Di Donato, who made everyone use it). I used to participate in some of the community project meetings that wound up being on Teams because it was the approved solution they could use. It was the reason why the openSUSE Project deployed a Jitsi instance.
They do not use Microsoft 365 or Microsoft Teams anymore. They use Google Workspace just like everyone else now (the mail headers tell you that). I don't know anything about their workflows, though.