Recent searches
Search options
Administered by:
Trentskunk
Whelp, time to go find another browser...
@trentskunk Welp, not surprised.
Vivaldi experiencing, as they put it, "a performance drag" from considering a proper implementation is the probable result of trying to pluck so much stuff in the browser, so they choose a status quo of OBEDIENTLY following Google's version of the Manifest V3 spec. How come they don't take a page from Firefox that keeps both Manifest V2 and V3 that doesn't impede extensions' capabilities as much as Chromium?
"We will keep Manifest v2 for as long as it’s still available in Chromium."
In English: "We don't do anything except change the wrapper for the browser."
It makes sense because they don't develop the browser. They just take what Google has and wrap it in a different shell.
Since Google is putting in all the work on the engine, Vivaldi just takes whatever Google gives them and barely changes it.
@lo__ @trentskunk Yes, they add so much fluff useful for some people and yet gamble with user experience that Chromium project introduces.
@vintprox @trentskunk The whole point of building on top of a project like Chromium is that you get the vast majority of the browser engine for free from the upstream project. Keeping MV2 in their downstream version of Chromium would require a substantial amount of work
Mozilla is able to continue supporting MV2 because Firefox is built on top of it's own browser engine. They don't inherit anyone else's decisions about what to support
Pedantic edit: there's no MV3 spec or WebExtension standard