According to the article, Cantor proved the theorem first and sent it to Dedekind. Dedekind suggested a simplification of the proof, which Cantor used when he wrote it up. The story doesn't make Cantor look good, but if the original proof by Cantor is correct, then the credit for the theorem still basically belongs to Cantor.
I came away with the impression that the biggest villain in this story was Kronecker. Without the need to tiptoe around his ego and gatekeeping, these results may have been published as a paper with joint authorship.
So, the apparent preference could simply be 5+ years more time to do hardware-assisted transcoding.
On the other hand, the federal government has gone after law firms that are not actually in violation of law and forced settlements due to their DEI programs, so you can't actually trust that you won't be hassled. Additionally, that you won't at minimum have the money clawed back, even if the claims are meritless, as the administration has done on Congressionally appropriated funds repeatedly as part of DOGE efforts.
If you take the money and spend it on research and development and then get hit by a clawback, whether due to "DEI" or some other reason, that is a financially ruinous event to somehow come up with $1.5 million dollars that was already spent.
A shame and a waste as it sounds like the project would have been beneficial outside of the Python ecosystem, had it been funded.
... but I still worry about backups. Having encrypted off-site backups is essential for this to work, and they need to be frequently tested as well.
There are good tools for that too (I've had good experiences with restic to Cloudflare B2) but assembling them is still a fair amount of overhead, and making sure they keep working needs discipline that I may want to reserve for other problems!
https://github.com/juanfont/headscale
As for backups, I like both https://github.com/restic/restic and https://github.com/kopia/kopia/. Encryption is done client-side, so the only thing the offsite host receives is encrypted blobs.
Does this mean when the passenger cancels or when the airline cancels? If it’s when the passenger chooses to cancel, this seems fine and fair: he paid for a flight; he chose not to take it. If it’s the latter, then it seems very unfair.
> Transparency of Fees
This seems patently unfair. Folks should know what they’re going to be paying ahead of time.
> Family Seating Guarantees
On the one hand, this seems fair. If you want to sit together, pay for that privilege. It doesn’t make sense to tax every other passenger for it. OTOH, families are a net benefit to society, so maybe it’s right for everyone else to pitch in a bit. Also, nothing is worse than the folks who didn’t pay up ahead of time who bug one, ‘may we switch seats so we can sit together?’ So perhaps free family seating makes life easier for everyone.
> [Elimination of] Accessibility Protections for Disabled Passengers
I wonder what that actually means. It could be fair (for example, folks too large for one seat purchasing two) or unfair.
I'd rather pay a monetary tax on my ticket to keep families organized together instead of the discomfort tax of sharing a row with parent+child that has been unexpectedly split up from their partner and is now trying to manage the child's behavior for the duration of the flight without the benefit of teamwork.
On the surface it seems reasonable to ask for an equivalent ID check online.
But. The bouncer doesn't photocopy my ID and store it in a poorly secured back room that is regularly raided by criminal enterprises or outright sold by unscrupulous owners of the establishment. Similarly, they don't check in with the government in a manner that leaves a record.
I'm fine with an ID check, but I think it is also reasonable to demand the same level of privacy that one gets when visiting a bar, casino, burlesque club, or similar establishment.