![](https://programming.dev/pictrs/image/85b43408-a5bc-4bf0-b3d0-0ea2713319ad.png)
![](https://awful.systems/pictrs/image/8651f454-1f76-42f4-bb27-4c64b332f07a.png)
Bookmarked. When the question comes up again, this article will be a good reply because it really brings many of my own thoughts to the point.
Same person as @Gobbel2000@feddit.de, different instance.
Bookmarked. When the question comes up again, this article will be a good reply because it really brings many of my own thoughts to the point.
I don’t think I’ve ever seen a game on Steam with “Overwhelmingly Negative” reviews before. Usually “Mixed” is already a good indicator to leave your hands off a game.
I must say I like the idea of having changes to files be bound to just the current branch, not the entire worktree (section 6.4.2), but other than that the points that are brought up don’t really seem too compelling. It certainly didn’t convince me that git has an inherently flawed design. For example, eliminating the staging area is a tempting point for simplifying git, but the authors already admit that it has some legitimate use cases.
But of course it is always nice to see some experimentation done in this space. I think the main reason why git sometimes is confusing, is because distributed version control really is a complex task, and git already does a very good job at making it tractable.
While there certainly is some overlap, Python is a scripting language and not a shell language. Some tasks that involve calling lots of different programs and juggling input and output streams are much easier done in bash than in Python.
I won’t argue with you that bash is janky and easily insecure, but what shell language do you think should replace bash?
A major political agenda of Vim is to support children in Uganda. A message about that is displayed whenever you open Vim’s start page. Bram Moolenaar insisted on users donating to the ICCF charity instead of to him, making Vim a very political editor in my view.