I live in Europe and never experienced such a thing. Perhaps to be more specific: I grew up in Spain and now live in the UK. To the best of my knowledge, children keep catching the flu every year and passing it on to their parents, who instead pass it on to their colleagues in the office (or used to, before 2020).
What it does it makes people mention this word less often. This is helping forget history.
To have it repeated sooner - in some other form, using different words.
They present on Windows because gpu (driver) vendors choose spend tons of their money to make them happen. And they spend their money exactly why? Because they see their profit in Windows pc market.
I would argue that Linux Vulkan support from Intel/AMD/NVidia is likely aimed more at Android than traditional Linux desktop distros.
Also, the whole point of Vulkan is to move these card-specific optimizations outside of the core driver while still letting games use kernel space to interface directly with the hardware (and doubtless platform vendors will put an abstraction layer on top of that like Metal on iOS). So the whole situation I'm describing has been a huge pain for a long time, but things are starting to get better.
Imagine there are giant creatures(like 5-6 meter tall) and they are proportionally stronger than you. They follow you everywhere and(though they wash and feed you) they also sometimes hit you with their huge palms?
I have quite a good memory of my childhood and my complaints about it are not over the occasional smack I received, but of the arbitrary and inconsistent nature of the punishment I received. Like the powerless everywhere, children are strong advocates of justice and rules and they absolutely hate inconsistent and arbitrary displays of power.
> Personally, what annoys me the most about TDD I've seen in the wild are two things
It's like saying that one is annoyed by programming in general because he's seen too many horrible things done with it! Anything can be abused, TDD is not an exception.
> your tests become more complicated than the tested code
Well, then don't tdd that code on unit level. Keep some high-level(smoke, integration etc) tests that executes it , relax and write/design it without TDD the best way you can.
> Tests affecting the structure - this is IMO a strong code smell.
Yes, and this smell (by definition) shows you a flaw in the code design. TDD helped to identify this. Apparently)