Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Brave is already substantially modifying Chromium to remove undesirable 'features' on top of adding the slew of Brave features. Manifest V3 is just another 'feature' that will be removed. The more significant issue there is that there might end up being conflicts between some Brave and Chrome extensions following this change.

I do not agree that writing a renderer from scratch is a wise idea. I mean in theory it's a great idea, but in practice? The Chrome renderer is very well done but, much more importantly, is also going to be what what 100% of web devs will test their sites with. Even browsers with quite large userbases, including FireFox/Safari/etc, tend to get B-tier treatment, if that. Of course standards alone should mean all sites ought render/behave the same with any compliant browser but... again, that whole theory vs practice thing.

There are also a couple of other major issues. Google can use their clout to rapidly change standards that third party projects must play keep-up on. But perhaps the biggest issue is Google using their monopoly in other fields, such as with YouTube, to change their products in ways that 'coincidentally' end up rendering poorly or slowly on third party renderers, as they have done multiple times. This [1] being one particularly stark example of such behavior.

The future of web usage is always difficult to predict. We've gone through numerous phases of seemingly unbreakable web domination from Netscape to Internet Explorer to Chrome. In my opinion Manifest V3 could finally be the tipping point of Chrome, but that may idealistic - we'll have to just wait and see.

[1] - https://www.neowin.net/news/mozilla-executive-claims-that-go...



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: