Re:Introducing chrome.scripting
by somehnacct3757 on Wednesday June 09, 2021 @07:01AM
(#27446511)
Or in this case, does less.
I think if Manifest V3 had 1:1 capabilities with MV2, less people would care.
Google has oodles of devs and infinite money; so their culture doesn't balk at rewrites. In the real world, treading water to stay on the Chrome Web Store with MV3 will muscle out huge swaths of a company's product roadmap. Our execs didn't even know what manifest versions are a year ago. Now Google is on everyone's shit list. If your API change is so jarring that non-technical people have to think about it, you're doing it wrong!
This is less of an API change and more of a platform redefinition.
Re:Introducing chrome.scripting
by heavyset_go on Wednesday June 09, 2021 @01:56PM
(#27450979)
> Instead of fixing an existing product, throw it away and introduce a new shiny thing, that does the same thing.
Introduce a new thing, that does the same thing but worse*. Google Music being replaced with YouTube Music is a great example of this.
Isnt that what google normally does? Instead of fixing an existing product, throw it away and introduce a new shiny thing, that does the same thing.