A really annoying thing I've run into is that lots of libraries/frameworks/etc will have shortcuts to introduce this delay, to avoid "pop-in" of lazy-loaded stuff.
Like, yeah, pop-in looks a little weird, but suddenly APIs are making that one Mass Effect elevator into a first-class feature...
The upshot of this is that women with a genetic advantage are banned, but men with a genetic advantage aren't; is this not straightforwardly sex discrimination?
No. Nobody is banned from the "men's" category, including unambiguously cisgender women of completely unambiguous sexual characteristics. They just wouldn't stand a chance, practically speaking (for example, in the 100 metre sprint, the all-time women's world record time would not meet the qualification standard). There was already "sex discrimination" in the fact of the women's category existing in the first place; this was done as a pragmatic matter so that the world has the opportunity to celebrate peak female physical achievements.
The debate is really around how the handling of intersex and transgender athletes intersects with the original purpose of creating a separate category for women.
>Nobody is banned from the "men's" category, including unambiguously cisgender women of completely unambiguous sexual characteristics.
This is exactly my point. Men with unusual characteristics are celebrated, but women with unusual characteristics are excluded into a non-competitive category.
You can justify it if you'd like, but in a practical sense, no man will ever get to the Olympics only to be turned away because they don't genetically qualify for competition. This is an indignity reserved only for women.
Respectfully, I don't think you're engaging with what I'm actually saying here.
No adults are training their way to the kid-lympics and then getting cut open and surprised by the count of the rings.
Also, the idea of "fairness" is overstated, a naturalist just-so fallacy. Is it "fair" that some male athletes are taller or shorter than others, or have other genetic advantages, for example?
You can do that, but the companies and institutions built on Windows will still keep paying whatever it costs for Active Directory, and thus all the bundled software that comes with it.
Individual consumer action does not a monopoly break.
It's very much a rock-and-a-hard-place situation. "It's an import", so they have to respond to it like they'd respond to imports...
But unlike physical imports, there's a sense that blocking these imports is an affront to base philosophical freedom in a way that prohibiting physical imports isn't.
> there's a sense that blocking these imports is an affront to base philosophical freedom in a way that prohibiting physical imports isn't.
It would serve UK legislators well to explore that tingling sense some more before they consider any further efforts in this direction, but that's just my two pence.
In addition to what others have said: even where remote play works, some games are worse candidates than others, and I expect Teardown would be towards the "worse" side of the set.
Teardown, visually speaking, is a pretty noisy game at times, and doesn't give a great visual clarity when streamed at real-time-encoding-type bitrates during these noisy moments.
FPS mouse+keyboard is also one of the worst-case scenarios for Moonlight/GFNow/etc. remote play, because first person aiming with a mouse relies very heavily on a tight input-vision feedback loop, and first person camera movement is much harder to encode while preserving detail relative to, say, a static-camera overhead view, or even third person games where full-scene panning is slower and more infrequent.
>We might see a day when HTTPS key pinning and the preload list is implemented across all major browsers, but we will never see these protections applied in a uniform fashion across all major runtime environments (Node.js, Java, .NET, etc.)[...]
It's actually not safe for clients to perform local validation because a quite significant fraction of middleboxes and the like strip out RRSIG and the like or otherwise tamper with the records in such a way that the signatures don't validate.
No! Because it's totally possible for operating system vendors to flip that switch without requiring every upstream project to adopt key pinning. It's MUCH less infrastructure to upgrade.
reply