Serious Discussion Resuming the transition to Manifest V3

[ForgottenSeer 97327]

Most likely does not apply to most here but Mr. Hill did put a kibbosh on unreal expectations for uBO Lite on the anticipated transition to MV3. I mean: this is still so fluid--MV3 first has to travel its way thru the test (DEV, Canary, etc) channels before it reaches the mainstream channels anyway. Who knows how long that will take past June (or whenever) 2024.

Spoiler

View attachment 279770

If anyone is interested, here is the link via the X post. I uploaded a snip of the post since some have made it ABUNDANTLY clear they don't have an acct. there.

Frequently asked questions (FAQ)

uBO Lite home (MV3). Contribute to uBlockOrigin/uBOL-home development by creating an account on GitHub.

github.com

Thanks for the link, in the FAQ-link something is mentioned about processing speed.

Extensions use JavaScript and Chromium internal engine uses C++ (Firefox also Javascript). As a rule of thumb C++ is 10 times faster than javascript. That is for un-optimized code. In IT code optimization is only done when response times are an issue. In application development it is considered bad practice to optimize code when there is no performance need, because (a) it does not add any value to the user, (b) optimized code is harder to maintain. Because there was a " who is the fastest adblocker race" uBO's code is probably optimized to last stretch. Also older code tends to be more optimized than newer code (programmer's like efficiency, so they often can't resist to optimize code, despite the fact that their project leader/scrum master don't allow them to spend time on it). That is why uBO's javascript code was faster than a newly developed adblocker in Rust (Brave?).

So will Mv3 be faster than Mv2?
Certainly not in Firefox (new unoptimized Javascript versus Gorhill's years of optimizing Javascript code)
Possibly marginally in Chromium/Chrome (because unoptimized C++ is normally 10 times faster than unoptimized Javascript).

Rust has memory integrity which C/C++ don't have, that is why many test were done how Rust faired against other programming languages (e.g. LINK)

 

[CyberTech]

Google plans to roll out Manifest V3, a new rules system for browser extensions, by mid 2024. The old system will no longer be supported by then, which means that all extensions for Chrome, the company's browser, need to support Manifest V3. Browser extensions that aren't updated by their developers will stop functioning.

Manifest V3 has been criticized heavily by privacy advocates and extension developers. Especially privacy-related tools, which includes adblockers, appear to be limited under Manifest V3.

While it is still possible to run adblockers and other privacy tools, these may no longer be as effective as before. Good news is that there are alternative browsers that users can switch to. Firefox, Mozilla's web browser, will also support Manifest V3, but also keep on supporting Manifest V2. In other words: Firefox users won't feel the impact of the change at all.

Chromium-based browsers like Brave, Vivaldi, Edge or Opera are in a different position. They may include a native content blocking option already, which is unaffected by the change. Extensions on the other hand may very well be affected, unless the developers hack Manifest V2 support into their browsers or alter Manifest V3 functionality.

The change impacts Chrome the most, but other Chromium-based browsers will also be affected.

For more information

Soon, Google has even more leverage against adblockers - gHacks Tech News

The article discusses a second lever that Google has against content blockers once the new extensions Manifest V3 lands in mid-2024.

www.ghacks.net