|
Top-level
@silvermoon82 YES! I'm glad I'm not the only person that can see this. It's a beautiful, elegant design... wrapped in a dumpster. Full of toxic waste. That's on fire. I'm waiting, eventually, the world will wake up and go "oh, what WERE we thinking?!?" and move on. But I suspect I'm going to be waiting a while. Git is AWFUL. Also, the Emperor has no clothes. 13 comments
@silvermoon82 Sadly, yes. Also, I think there's a LOT of Stockholm Syndrome. "I've invested SO much time and pain learning this tool. Therefore, I must be 1337, and because it proves I'm worthy (& other people struggle with it, therefore proving I must be better than them), I will defend this tool to my death."  @jhulten @sidawson @silvermoon82 No, the guy who wrote the kernel wrote this because his favorite tool became unusable for political reasons, so he made an open source version of it. Nobody ever claimed that git was a good SCM. It was only ever designed to fit the linux kernel's needs. Nobody else was ever considered. Hence it surprised a lot of people that so many projects switched to git, thus adding complexity that they didn't need. @sidawson @silvermoon82 the sunk-time problem is such an easy trap to fall into and so hard to leave @bynkii @silvermoon82 and the more time you spend in the trap, the harder it is.... (see what I did there? :) ) @sidawson @silvermoon82 not to belabor your points, but have you tried any of the gitwrappers like gitUI that wrap it in a GUI, and I think there's a project that is just better syntax for it? the beauty of git being a terrible command line is that other people can know it and friendlier fronts can exist -- even the aliases in the zsh/fish/etc plugins get you pretty far, though googling around you can probably find an alias file for them too more people should rec them to new people to get it. @NireBryce @silvermoon82 Yeah, I use two separate gui interfaces (lazygit - amazing, and Sublime Merge - useful for visualisation & history). Even with those, it's terrible (although certainly MUCH less painful than either creating endless scripts to manage a typical workflow, or endlessly typing at the cli). Also, inevitably, sooner or later there'll be some break that requires DEEP knowledge to fix without causing more mess. It's just horrible & no UI can fix that right, but what I mean is, right now most intros/advice recommend *git cli*, even though not that many of us seem to use it directly, and *that* at least can be reduced by shifting the advice we give @sidawson it's true, but it's also all we've got until someone writes a better front-end. |
Gregory's Server
@sidawson
It's awful, but it's established and has a self-supporting user community. Replacing it will take something world-changing.