4 ms·
Hard forking isn't a practical consideration unless the organization in question is willing to build a team that can rival Google's Blink/Chrome team, which is
by kitsunesoba 4y ago
Hard forking isn't a practical consideration unless the organization in question is willing to build a team that can rival Google's Blink/Chrome team, which is a ridiculously tall order. Microsoft is capable of doing that but I don't think they want to.
- jjcon 4y ago> which is a ridiculously tall order And yet a ton of people here think there should be lots of people building lots of completely separate browser engines… that is certainly more difficult To the point though - I think the threat of hard forking does something in and of itself to the chromium maintainers
- kitsunesoba 4y agoThe main issue with hard forking is keeping up with Google's unrelenting firehose of changes, many of which have serious security implications, which is going to become more and more difficult as the fork diverges. Maintaining an original web engine is certainly no simple task, but it's more reasonable than having to deal with the output of a much larger and more well-funded team.