Why SQLite Does Not Use Git

Re:Why SQLite Does Not Use Git by inferiorhuman on Saturday July 22, 2023 @09:56PM (#36831875)

On the one hand I'm inclined to agree about monoculture, on the other I've worked at a company where one employee dictated that we use bzr. Basically everything was an order of magnitude more difficult through minimal fault of bzr. None of the third party tooling worked with bzr, or if something did have bzr support it was dropped ages ago.

It's kind of the same situation with Github. The pain in moving away from it as they continue to slaughter the UX is still pretty great.

So yeah monoculture is bad but progress is painful.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by paulryanrogers on Sunday July 23, 2023 @12:08AM (#36832478)

Having been that person (albeit before Git was the one true way), I'm sorry. But seemed so nice and had solid externals and sparse checkouts back in the day. And as bad as it got for us, it still felt easier to pick up and use than early Git.

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by inferiorhuman on Sunday July 23, 2023 @01:05AM (#36832693)

Sure, and I was that person with the svn -> git migration at a different gig. Ideally our behavior matures over time.

For me, at least, two things made git really manageable: github and the O'Reilly book. After those git was a no brainer. Even now, if you don't need the integrations it's not so unreasonable to use something else (altho bzr's been discontinued).

[ Parent | on HN ]

Re:Why SQLite Does Not Use Git by Brian_K_White on Monday July 24, 2023 @11:41AM (#36849768)

To me that just sounds like an example of the reason to avoid tight coupling.

If something breaks beacause it cares that I use git and only git, then it's that something that is broken and to be avoided, not the git alternative.

[ Parent | on HN ]