You mean like by hiring a significant chunk of Debian maintainers, including the most active apt developer, by having their employees maintain a significant chunk of Debian packages, and by explicitly upstreaming their patches to Debian?
I was supposed to get a device with 64 gigs of RAM later this year. I just got an email telling me that due to the RAM shortage they've cancelled the 64 gig version.
Heh you're right, I didn't catch the bitwise and, so I thought you were making a TypeError joke about comparing strings. Fixing the and though (which I did naturally when I typed it into my interpreter to double-check), we get the issue that they are just using a string for the time rather than a time object. "Too early" is also a valid entry that gets us an available office.
Canonical employees have been part of making Wayland since before Mir existed. Mir came about because Canonical wanted to have something that actually worked within a reasonable amount of time. The result? A bunch of places where groups with lots of resources will contribute to Linux (such as automotive systems) use Mir because it was actually practical to use within a reasonable timeframe. A lot of the recent progress in Wayland has come because the people who were holding it up for years finally gave up and listened to the practical concerns from experts who work at places like Canonical and Nvidia.
And snaps still do things that Flatpaks don't, such as being able to package a kernel and system services. So even if Canonical wanted to switch to flatpak, they couldn't. Not without making changes that are fundamentally contrary to the design of flatpak.
I didn't mention the Unity thing because while I don't agree with your assertions, I do think it's an example of how someone at Canonical's hate for KDE has prevented them from making the same good decision at least 3 times.
If you want to pretend it's Canonical vs. nonprofits, you're going to have an ugly surprise when you find out which corporation hired most of the people who held up Wayland for so long and has its tentacles so deeply in Flatpaks. (HINT: it's not SuSE)
Mir came about because the people behind Wayland were fucking around for years without making progress. Now that Wayland has actually matured, Mir is a Wayland compositor.
Snaps predate (and do a whole lot more than) flatpak.
At distances closer to a quarter wavelength you can also have some pretty gnarly reactions if a line goes down. That's why stuff like the Kahora Bassa power plant uses HVDC for transmission.
You mean like by hiring a significant chunk of Debian maintainers, including the most active apt developer, by having their employees maintain a significant chunk of Debian packages, and by explicitly upstreaming their patches to Debian?