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

Could someone explain in simple terms, what’s so tricky about spinning off a v2-compatible chromium fork?


Forget about forking, just offering a build of Chromium for a single platform and architecture that gets the security updates in time is a lot of work.


People who remove v2, own ad networks, develop chrome and write standards are the same people. It’s new age mafia, cancer of the internet and they do everything for you to not be able to just spin off a fork.


So what would they do?


Already done: used lying tactics to make their browser and ad networks dominate, bloated the standard to make browser development unsustainable.

Right now: rooting out the entire possibility of running full adblock-capable extensions from the sources, so that even chrome-based browsers could not support it back.


Chromium is maintained by the largest ad company in the world.


It’ll drift apart over time and become ever harder to track the upstream without engineering effort


google can weaponize structural changes to make any v2 maintainer's life a living hell, the code base is massive.




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

Search: