I hate AudioContext. Visitors might like it since it does not permit websites to blast loud sounds. However, as a developer, I hate it. Before AudioContext existed everything was cool. Suddenly it appeared from nowhere. I had no clue that Chrome added it. Now my websites aren't as exciting at first glance anymore.

if your website needs audio to be "exciting", it just doesn't have any content worth looking at.

(obviously an exception is if the sole purpose of the website is providing audio)

Everyone hates when a website just starts playing out of nowhere. And the mere fact you don’t read the updates is just ignorance.

I guess devs like you are the reason why Google made that update in the first place, and rightfully so.

Autoplaying media is the second-worst thing about the Internet (user tracking is #1) and I'm glad browsers are putting a stop to it.

I remember the time quite vividly when I installed windows 10 at 3 o clock in the morning and I nearly pissed my pants and had an panic attack when the Cortana voice talked to me - audio settings weren't right.

5.1 surround sound system, full volume - I guess > 100 decibel.

Yes. Exactly for those reasons I never want to have a software or anything else think it's a good idea to blast audio without explicit permission.

I was pretty lucky that my neighbors seemed to not care at all.

Took me quite a while to get calm after that shock.

@IntrusionCM Not only that, but when I have my own music player running in the background, I certainly don't want some shitty website to crap out audio just to fucking pretend to be "exciting".

The rule is that you can't start playing audio for any reason other than a user interaction. If your usage doesn't meet this requirement your design is wrong.