4 ms·
"The mental model for Git is needlessly complex" News flash: Many programmers love complexity. Complexity == popularity == profit Prove me wrong, please (I
by 1vuio0pswjnm7 5y ago
"The mental model for Git is needlessly complex"
News flash: Many programmers love complexity.
Complexity == popularity == profit
Prove me wrong, please (I seek simpler stuff)
- strictfp 5y agoI think the mental model is "I can use this tool, since it's hard it will make me look smart"
- loudthing 5y agoPeople who have stuff on their monitors specifically so others think "they must be really smart" are the scum of the earth.
- deleted 5y ago[deleted]
- throwawayboise 5y agoMany new/inexperienced programmers love complexity. I used to get into exploring every nook and cranny of every config file and endlessly tweaking settings. Now I strive to use everything with default settings if at all possible.
- da_chicken 5y agoYup. When I have to install it for the sixth time the last thing I want to do is remember what I had to configure the fifth time and what I had learned that I needed to stop configuring from the third and fourth times. Now I want my operating system and my tools to shut up and get out of my way because whatever irrelevant thing they think is important is not what I ever need to be working on.
- hn_throwaway_99 5y ago> Many new/inexperienced programmers love complexity. Not sure if you're trying to argue that Linus was a "new/inexperienced" programmer when he first wrote git. I think the "it's too complex" argument against git is misplaced, or at least not complete. I don't find git "complicated for complexity's" sake (e.g. looking at Enterprise Java Beans back in the day), but it has a very specific workflow in mind for its conceptual model, and if you don't understand that conceptual model, you're just going to be confused. It took me a while to grok that model, but once I did it clicked and I understood it. Not saying it's optimal, but it also has a lot of benefits.
- throwawayboise 5y agoOpenBSD uses CVS to develop an entire OS, kernel and userland. Git's complexity is not required.
- da_chicken 5y agoExposing the user to the totality of the complexity of the problem is, perhaps, the most complete and indefensible failure of an otherwise successful software design that I can imagine.
- couchand 5y agoAll abstractions are leaky, but an abstraction meant to never lose the work of a power user is maybe more defensibly leaky than average.
- whynotmaybe 5y agoWhatever I read about Linus seems to imply that he is far smarter than me but git is a great tool for his personal purposes. This is an 18wheeler that can haul anything but for "basic" dev doing simple administrative apps, a bicycle VCS is more than enough. A lot of dev I've met don't even understand the deep ramifications of multiples branches with any VCS so understanding the complexity of git is way above what we require of them. Git has a lot of benefits but I'm not quite sure that it's really a good thing that it is slowly becoming the de facto standard. Wait and see...
- TheDudeMan 5y agoWow. Maybe this is why most software sucks.
- geitir 5y agoI would say it's more like complexity == feels like I've accomplished something
- LAC-Tech 5y agoI think you're right. And as much as I want to think I'm ruthlessly simple, I do notice this in myself as well. Everyone will agree with us of course, but suggest something minor like "hey maybe you don't need react" and here come the reservations. To paraphrase Alan Kay, everybody likes simplicity except for the simplicity part.
- Koshkin 5y agoDo you mean the UNIX way (cp, diff, patch)?
- manquer 5y agoYou are right there is a correlation but not because programmers love complexity. It is easier to design complex systems and harder to simplify. Also complex systems have positive economic incentives like consulting training books or that if simple will not be sustainable.
- tshaddox 5y agoThe entire job is managing complexity, either by developing good abstractions for adding and maintaining necessary complexity, or by removing unnecessary complexity. I love this process, so I guess you could in some sense say that I “love complexity,” but not in the sense that I increase complexity whenever I can.
- nijave 5y agoI think some of it also comes from treating symptoms instead of problems. "Git doesn't do X so I'll just make this tool to add the feature" One hundred tools and a few consolidations into toolkits later you have a massively complex tool chain scope creeped from some much smaller problem deep down in git
- yalok 5y agoMy observation is that it all depends on scale. Huge projects (such as Linux code base) can’t survive with simple solutions (e.g. non-distributed VCS). Loving complexity for the sake of complexity or sake of job-security or competitive advantage covers only small subset of situations. There’re a lot more cases where seemingly simple problem has a lot of hidden complexity, and only complex enough solutions succeed at successfully solving it and staying competitive on the market…
- wyoung2 5y agoComplexity is fine in something like a programming language or a text editor where increasing mastery can mean better software and hopefully more money. How do I make more money by learning arcane Git commands? We don't use DVCSes for their own sake, we use them to accomplish something else. To the extent that the DVCS gets in the way, it's an opportunity cost.
- dreyfan 5y ago> Complexity == popularity == profit Entire node/js/ts ecosystem resonates strongly here. They reinvent the wheel, assign it a new name, thought-leaders market those inventions to every corner of the tech ecosystem, and then they add another few layers to their build chain.