I agree on the dislike for the change, although it's not a big hassle for us at work. The bigger headache for me is updating side-projects: I get little enough

I agree on the dislike for the change, although it's not a big hassle for us at work. The bigger headache for me is updating side-projects: I get little enough time to work on them and when I do have time I want to be doing interesting stuff, not jumping through bureaucratic hoops. It's just no longer the case that you can put anything on the web, apart from basic static content, and have any hope it'll still "just work" in 5 years time because a bunch of do-gooders and busybodies at Google, Mozilla, Apple and the like are constantly fettling behaviour that's been standard for years with sometimes debatable justification. This is one issue. Others I've had to deal with in the past 2 - 3 years that spring immediately to mind: blocking access to audio context, blocking access to device orientation[1], (lack of) reliable full screen support on iOS. It gets tedious. [1] This one caught me completely off guard: I'd had no idea any change was being made here until some time after it had happened.