Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
Help starving lone devs keep up important projects.
The big fish are Ublock Origin and AdBlock Plus, as well as YT front ends like yt-dl, Invidious and Newpipe, but by favorite project is https://github.com/uazo/cromite
I think YouTube is eventually going to assert control through Chrome, and the community is going to be caught flat footed with everyone still relying on Chrome extensions.
I think that's a relatively simplistic way of viewing this. Although I don't disagree with the core argument, Google will always implement and ship "standards" that fit their business model or their vision of the web. A Chrome API becomes a defacto standard regardless of the state of consensus between engine vendors. Chrome can bulldoze through the standards process because of the massive amount of Chrome installations (and derivatives). There are standards that have never been fully accepted by Mozilla [0] or WebKit (famously webusb for instance, because of security implications) but they are still in Chrome and now Firefox or Safari are effectively a "worse" browser because it doesn't support "standard" X that never reached consensus but Chrome implemented anyway. It always starts as an "experimental" feature under a config flag while the supposed discussion is taking place "just to see how it works, promise" before Google decides to remove the experimental flag and ship it. WEI started to play out exactly in the same way but given the massive outrage they decided it was too damaging to keep pursuing it (they still sneakily implemented it in Android WebViews).
So although I don't disagree that, yes Google has certainly improved on some things when it comes to standard processes they have abused their powerful position and continue to do so to push forward whatever they think it benefits them.
[0] https://mozilla.github.io/standards-positions/