BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)
BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)
Posted May 29, 2024 23:17 UTC (Wed) by flussence (guest, #85566)Parent article: BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)
He was wrong on the assertion that it was an “open source community problem” that compelled him to burn bridges — the open source community has absolutely no qualms about playing and paying into Microsoft's proprietary ecosystem, to the point where GitHub now dominates the planet in a very real sense. They even let their direct competitors use their service for free. (Microsoft!! Remember what we thought of *them* at the time?)
Unless your audience is mostly government and military, you need a robust set of soft skills to participate in the software industry - those are not things you can tabulate in a spreadsheet, and if you don't make time for them your numbers will end up disastrous and you won't understand *why*, because an entire concept is missing from your vocabulary. Why point this out twenty years after the events in the article? Because organisations involved in FOSS today are still making the same mistake!
Posted May 30, 2024 12:40 UTC (Thu)
by farnz (subscriber, #17727)
[Link]
I want to give this more visibility, because it's something I see many software developers completely ignore; once a project gets large enough to have multiple developers working on it, your soft skills to get the other developers to work with you, not against you, often outweigh your coding ability. It's better for a project to have 3 developers each splitting their time 50:50 between coordinating work to avoid conflicts and actually coding, than to have 3 developers spending 100% of their time coding, but each undoing the work of the other two to make their code work.
Even at his worst, Linus understood this; his role in Linux for a very long time has been to coordinate developers so that there's a coherent project, rather than to cut code.
Posted May 30, 2024 15:32 UTC (Thu)
by Wol (subscriber, #4433)
[Link]
I read some of the stuff. In it, I think it's McVoy himself that says that he and Sun both fell victim to the same problem - it's hard to surrender a flowing profit stream, even if you can see disaster looming ...
When the time came, he walked the walk. Because he no longer had any choice ...
Cheers,
Posted May 31, 2024 13:33 UTC (Fri)
by skx (subscriber, #14652)
[Link]
I'm sure they had customers/paying users in the early days, but it seemed like the project never really took off outside a few places, and of course later git took over the world eclipsing almost all other systems. Mercurial is still limping along, but things like darcs, bzr, cvs, svn, are all obsolete these days.
BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)
you need a robust set of soft skills to participate in the software industry
BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)
Wol
BitKeeper, Linux, and licensing disputes: How Linus wrote Git in 14 days (Graphite blog)