3 ms·
I think you’re discounting that everything Chrome does these days is designed to become a web standard, unlike IE which was trying to have browser-only features
by skybrian 5y ago
I think you’re discounting that everything Chrome does these days is designed to become a web standard, unlike IE which was trying to have browser-only features for lock-in.
Chrome does seem to be somewhat hasty, which can have a similar effect in practice. But it might seem different if you actually want a feature and don’t want to wait years for it?
I don’t think Web Audio is as bad as you say. There is the ScriptProcessorNode which is getting deprecated in favor of audio worklets because having JavaScript processing audio on the foreground thread is a bad idea. But other than that, it seems nice for making simple audio processing graphs, and the infrastructure for putting JavaScript in the background took a while to work out.
- kevingadd 5y agoJust look at how many revisions the W3 spec has had. It had even more churn that wasn't visible there... IIRC it originally shipped with synchronous audio decoding on the main thread for some reason. Chrome has also shipped multiple p0/p1 level bugs in Web Audio that users had to wait weeks or months for fixes to, like a while back when they introduced a priority inversion while rewriting their whole mixer so audio was just completely broken for a double-digit % of their userbase. They also treated basic use cases like 'pause a piece of playing audio' as out of scope, which is simply bizarre. Every web app or port I've ever touched had issues caused by the poor design and quality of the API.
- skybrian 5y agoOkay, as someone who just used it for a few demo projects, I didn’t push it very hard. Thanks for explaining in more detail.
- dmitriid 5y ago> I think you’re discounting that everything Chrome does these days is designed to become a web standard Indeed. It's rarely designed to be a web standard. However, Chrome rams that through standards body, calls that a standard and enables it by default in Chrome. Just look at WebHID. Firefox devs couldn't even understand the spec [1], it was so Chrome-specific. Guess what, it's enabled by default in Chrome [2] and Chrome says that it's a standard now [3]. Most of those non-standards are not even out of the "draft" stage of the standards process, with both Safari and Firefox objecting to many, many, many things in the specs. Google. doesn't. care. [1] https://github.com/mozilla/standards-positions/issues/459#issuecomment-753864467 https://github.com/mozilla/standards-positions/issues/459#is... [2] https://webapicontroversy.com https://webapicontroversy.com [3] https://web.dev/hid/ https://web.dev/hid/
- skybrian 5y agoThe comment in [1] is from January and the spec is dated March, so perhaps they saw an early draft? I only took a quick glance, but it seems fairly readable now. It would be nice to be able to connect game controllers to web pages. The fact that they tried and failed (if they did fail; maybe they will succeed eventually?) shows that they cared at least a little about standardization, even if it was somewhat half-hearted. When negotiations fail, it's not a given that one side is entirely at fault.
- dmitriid 5y ago> The comment in [1] is from January and the spec is dated March, so perhaps they saw an early draft? The "request for Mozilla's position" was on December 1, 2020. Chrome enabled it by default in Chrome 89 that was released only 4 months later, on March 3, 2021. So they "requested Mozilla's position" and still went ahead, implemented it and enabled it by default. But so nice of them to update the spec two weeks after they released it. > The fact that they tried and failed (if they did fail; maybe they will succeed eventually?) shows that they cared at least a little about standardization As reality and facts show, they couldn't care less about standardization. > When negotiations fail, it's not a given that one side is entirely at fault. Please show me at which point this was a negotiation.