> Linux kernel history has lived without it, so I'm guessing the "our code is so complex we need it" is a false idea. Those guys are still sending commits (pat

> Linux kernel history has lived without it, so I'm guessing the "our code is so complex we need it" is a false idea. Those guys are still sending commits (patches) to each other by mail, I think they willingly live in such a special and weird bubble that it just can't be compared to any "real life industry project". We've recently started to enforce linear history on our main branches at work, because it makes analyzing broken builds such a breeze. The mantra is "Insertion is hard, analyzing/understanding is easy" (for a merge-based history, it's pretty much the other way around), and so far it's quite the success. It did take quite a bit of effort though to get everyone up to speed, and it still requires the occasional help to clean up the commit history of some merge request, but it was well-worth the trouble so far.