TechNom (nobody)

Git has a problematic UI. But the good news is that everyone acknowledges it and there has been genuine and sustained efforts to improve it. Git today is much more pleasant than it was before 2010.

I wonder what sort of problems they had with C++ that prompted them to port such an old codebase to Rust.

I think that you can add a WIP prefix to the MR title to prevent the maintainers from accidentally merging the branch prematurely.

All the problems mentioned here are common to various tech jobs and possibly other fields as well. It’s nothing specific to programming. All problems mentioned are societal issues and not inherent problems of any profession. Things like student loans, hustle culture that leads to burnout, over compartmentalization of work, clueless managers, etc. We need a social revolution, not a career change.

It’s reported to be a declarative block list that’s already vastly powerless compared to regular ublock. Its presence shouldn’t give you a false sense of security. One thing that is sure to happen is that its capabilities will be gutted in the long run - perhaps by just bypassing the blocks.

I assume you are talking about dependency versioning. That’s hard on regular Linux distros. However, it’s easy on nix and guix.

Gamers and typists/coders are completely different species. Besides, WASD keys don’t use lateral extension (assuming gamers use touch typing at all). Have you checked out any KB layout communities?

That would be a bad design, IMO. The index finger has 2 keys to manage, of which one needs its lateral extension. Though the pinky is weaker, the semicolon is in its resting position.

The actual answer though, is Bill Joy’s keyboard. Another commenter has explained it.

What are the other reasons?

I saw the discussion that led to this, live on fediverse. Confusion and surprise were the dominating themes. Even the best git gurus were taken by surprise and even a partial clarification needed checking the git source code. It says how difficult git is as a tool. It’s likely that the git developers are the only ones who know how to use it correctly. While this is not unusual for custom tools, it shows how much thought should go into UI design for public software.

I’m surprised that the 3-way merge isn’t well known. In the earlier days of Git, the 3-way merge was its selling point, over contemporary alternatives like CVS and SVN (where people used to avoid branching, since merges broke far too often). There is a command called diff3 that can do 3-way diffs and merges. Many GUI diff tools like Meld and KDiff3 have built-in 3-way diff functionality. The git book also talks about how this is done.