News for hackers. Stuff that matters.
Re:Software Engineering at Google (2017) by tieze on Friday January 04, 2019 @06:51AM (#18823369)
It might be a practical thing. I've heard from a Googler (a couple of years back) that getting changes in can take ages, and by the time the change lands, there's a good chance that there are merge conflicts, and the cycle starts over. Branches would make this even more painful.
Re:Software Engineering at Google (2017) by hknd on Friday January 04, 2019 @06:57AM (#18823393)
Depends on the size of the change. Small changes are preferred in most trunk-based-dev companies.

FYI: There are (multiple) tools in Facebook and Google which are an abstraction on top of their VCS. (e.g. which feels more like git, where you can work on a stream of changes which depend on each other without actually pushing anything to head)

Re:Software Engineering at Google (2017) by nradov on Friday January 04, 2019 @12:07PM (#18825609)
Branches actually make this much less painful. Just reverse merge from the trunk back to each branch on a frequent basis.