Choose Firefox Now, or Later You Won't Get a Choice (2014)

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by tomc1985 on Friday December 07, 2018 @02:39PM (#18630831)

"- No, you can't just "fork Chromium" if you don't like the way Google is running the project. Web developers will still make their website work well with whatever Google releases, regardless of standards."

Hah, even compiling Chromium takes a huge amount of effort and a workday or so of time. Don't think I'd want to go spelunking through that codebase

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by jolmg on Friday December 07, 2018 @06:27PM (#18632630)

I would imagine that compiling Firefox is just as difficult.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by sometimesijust on Friday December 07, 2018 @08:38PM (#18633297)

Firefox is much easier and faster to compile but still complicated enough that you need to follow their build guide. Chromium is held back by Google's overzealous build systems that assume everything is built on a unified build server and permanently cached somewhere on their corporate network which results in actual build times being unoptimized.

[ Parent | on HN ]

Re:Choose Firefox Now, or Later You Won't Get a Choice (2014) by cztomsik on Monday December 10, 2018 @08:33AM (#18647742)

Firefox is moving to rust, and for example adding webrender to your project is just few dependencies away, so I'd expect building firefox will only get easier, unlike to google projects where everything is built with their custom tool

[ Parent | on HN ]