I wouldn't want a browser without extensions. Ad blocking in particular.

To me, ad blocking belongs in extensions. The job of a web browser is to show web pages as intended according to the standards. It includes all the ads, tracking, etc... the page has put in. If you want to block stuff or deviate from the standards in any way, that's what extensions are for.

And extension like ad blocking are an arms race, websites will deploy countermeasures to make them less effective and to which extensions can respond. Again I dont want the core browser to participate in an arms race. Keeping it free of vulnerabilities is already hard enough not to fight against standard behavior.

▲

ocdtrekkie 3 hours ago | parent [-]

Extensions are the primary threat to your security today. Nothing else comes close. Organizations are not basically competent if they are not restricting or blocking extensions, and you should not have more than one to three very trusted extensions in your browser. I'd argue the case for eliminating them in favor of in house code is significant.

As a reminder: Extensions execute with post-decryption access to the websites you view, and they update to new code silently and without asking for permission. HTTPS might as well not bother existing if you have extensions you do not have incredible trust in.

	▲	GuB-42 2 hours ago \| parent [-]
		I would argue that building in extension-like features inside the browser is worse. In both cases, that's extra code, with security implications, but in case of extensions, you can choose not to have it. Now, that's a question of whether you trust those who write the browser more than those who write the extension. And by the way, the argument you have is the same that justifies the much hated "manifestV3", which makes extensions less powerful for security reasons. But it also limits the blocking capabilities of browsers to a simple, less effective blacklist. That Firefox still supports the old "insecure" way is a big selling point over Chrome.