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

Or they just don't want to admit publicly that they're too small to maintain a fork when it diverges this much


Well Vivaldi is open source, right? Personally I would be reaching out to Brave, who already plans on maintaining V2 support, and see about a joint venture with a forked chromium.



Ah. They can go fuck themselves then. I had assumed given the fact that the source was available.


c++ sources are available.


> Even though our license doesn’t strictly allow this, we welcome it and we encourage users to share these code modifications on our forums.

lmao wtf


I was intensely interested in this, and after much reading, here's my best understanding:

Neither Brave nor Vivaldi are proposing to maintain engine support for v2: they both point to the codebase retaining support after Chrome drops support (likely for enterprise) as being the driver of their ability to offer v2. Both say that once those codepaths are removed, so too will v2 support be removed from Vivaldi and Brave.

No idea when Google will make that call.


Alright, so they’re both literally just useless wastes of man-hours then. Good to know.




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

Search: