4 ms·
This is the 2nd article I’ve seen in recent time bikeshedding the minutia of the git development process as part of criticizing the git learning curve. I fear
by dogleash 5y ago
This is the 2nd article I’ve seen in recent time bikeshedding the minutia of the git development process as part of criticizing the git learning curve.
I fear we’ve reached the point that people are starting to realize the grand new UI to make git easy will always be a pipe dream and that no UI can actually make git intuitive to a noob, but they aren’t going to put away the knives either.
I’m not saying that git has zero fault for more of a learning curve than nessicary, but blaming git itself for the fact nobody can be arsed to learn it is an industry wide cop out and an embarrassment.
- forgotmypw17 5y agoI've been using git for years, but I'm still a noob. I've found that IntelliJ has by far the best git UI for me, to the point that I use it for everything, including Perl. If anyone reading this is feeling stuck in git and just wants to get it done and move on to more coding, I highly recommend it.
- felipec 5y agoIsn't this a bit of a false dichotomy? It can be *both* that git users should do a better job at trying to learn git, and that git developers should try to make the interface more user friendly. Personally I prefer to focus on what developers can do because any change in the user interface done by one developer can potentially impact thousands, if not tens of thousands, if not millions of users.
- dogleash 5y ago> Isn't this a bit of a false dichotomy? No. I explicitly mentioned that git was not blameless. My post was about the fact we’re moving towards the realization that after 15 years of trying, we’re not going to find a grand design overhaul that makes git’s concepts easy to pick up without putting in effort.
- felipec 5y agoEveryone already agrees "staging area" is the best term. That's the whole point of the post.