Will Manifest V3 Kill Chrome? | Theo - t3․gg

The recent changes to Chrome's extension framework, specifically the transition from Manifest V2 to Manifest V3, aim to enhance both security and performance for users. Manifest V3 introduces stricter rules regarding code hosting and obfuscation, requiring all extension code to be included within the extension itself, which simplifies auditing and reduces the risk of malicious activity. The new framework also replaces traditional background pages with service workers, improving resource management and performance.

However, these changes pose challenges for ad-blocking extensions like uBlock Origin. The new declarative net request API limits the ability of extensions to dynamically filter requests, which may hinder some functionalities that users have come to expect. While the changes are designed to mitigate security risks associated with extensions, they may also complicate the user experience, particularly for those relying on advanced ad-blocking features.

Despite concerns about potential motivations behind these changes, experts argue that the Chrome team's primary goal is to improve the overall web experience and address longstanding security issues. The transition to Manifest V3 is set to begin next year, with Firefox and other browsers indicating they will continue to support Manifest V2 for the foreseeable future. As users adapt to these changes, the implications for ad-blocking and web security will continue to unfold.

Will Manifest V3 Kill Chrome? Theo is a software dev nerd mostly known for full stack TypeScript stuff. Check out Theo and his stack at t3.gg --------

-------- Keywords: shadcn, full stack development, cursor, firefox, bun, claude, developer podcast, programming Learn more about your ad choices. Visit megaphone.fm/adchoices