For me (and I suspect a few other people working with react, but certainly not everyone), the main issue with hooks is exactly that class components were fine, and hooks are fine, and we did not need nor want more "fine".
Hooks feel more like something added to fill in space and another example of the ecosystem bloating itself just for show.
Linkedin has also been doing this for years - tens upon tens of different "communication preference" options. They keep adding more, or renaming existing ones and defaulting them to on.
It's 90 days, 60 days on small islands and you can only go over that limit if you're low-income. Compliance is a different issue, because Greece, but hopefully AirBnB and the other platforms will help police this.
Firefox was kinda slow sometimes with too much JS on the page on my old phone but still overall usable, and that was a J3 (replaced just last week), so I'd say that's pretty good. Great and lag-free on my s10+ so far. Not convinced optimization should be a priority over features and addons.
> If you want them to change you have to reduce the stakes for them.
Why? It just has to become unprofitable for them to look for something else. They will adjust their stakes accordingly (are you proposing getting them a different source of income? wouldn't someone greedy just accept both?).
"The national Football League (LaLiga) was fined for offering an app which once per minute accessed the microphone of users' mobile phones in order to detect pubs screening football matches without paying a fee"
Yes, proof of weaponized gdpr use indeed (for very specific filtering cases of gdpr use).
Hooks feel more like something added to fill in space and another example of the ecosystem bloating itself just for show.