Richard Hipp - Git: Just Say No
Why Hacker News recommends it
Recommended for the SQLite author's reasoned case for a different approach to version control, and as an introduction to Fossil.
What it is
SQLite author Richard Hipp's talk at SouthEast LinuxFest criticizing Git's workflow and introducing Fossil as an alternative. He lists Git enhancements and argues for keeping history intact.
Recommended by 3 HN commenters across 3 different months, 2020 to 2021.
What Hacker News said
Recommends asix66 · 2020-02 · on “The History of Git”
This reminds be of a talk I watched by Richard Hipp, "Git: Just Say No" [0] where he discusses a "top 10 git enhancements" list, as of the time (4 years ago.) It's a good talk, and caused me to discover Fossil SCM. Sadly I've yet to try/use Fossil, and my teams still use git. [0] [this video]
Recommends brigandish · 2020-03 · on “Please stop recommending Gitflow”
> Take a look at this image and tell me it’s immediately intuitive I'm using Git, there's nothing intuitive to be found here. On a possibly related note, I watched a talk by D. Richard Hipp (I don't remember which one - edit: probably "Richard Hipp - Git: Just Say No"[1]) where he compared it with Git (a lot) and explained how Fossil keeps everything, there's no throwing away of history, no need for rebasing (at least as a workflow). It sounded nice - refreshing, even. I'm going to start using it for some projects and see how I get on, because frankly, I'm tired of Git and this need to strategise saving copies of my work , because that's basically what it does. Sometimes I even pine for the
Recommends belter · 2021-07 · on “Git vs. Fossil: what you should have done vs. what you did”
Here is a (somewhat old) talk by Richard Hipp, the author of SQLite about Git: "Richard Hipp - Git: Just Say No" [this video] I use Git every day, but I am curious about Fossil and have been researching it for a while. I am not planning on changing, as I need to get to the bottom of some data corruption events I have seen in their forums. Not saying it was the fault of Fossil, just that it requires more research on my side. We should not forget Version Management did not start with Git but has a vibrant history that began with SCCS, RCS, CVS, ClearCase, Perforce, SVN, etc... As I used all the systems above except for SCCS and RCS I would advise for some caution here on thinking Git core flows are