Live data from Hacker News

Why SQLite does not use Git (2018)

sqlite.org

21–30 of 454 posts

Re: Why SQLite does not use Git (2018)

#21
I'm glad Fossil works for them, but this line is bothered me:

> In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. That one binary contains all the functionality of core Git and also GitHub and/or GitLab. It manages a community server with wiki, bug tracking, and forums, provides packaged downloads for consumers, login managements, and so forth, with no extra software required

git, for all its issues, is not bundling the kitchen sink. I do prefer the "do one thing and do it well" approach.

Re: Why SQLite does not use Git (2018)

#22
Previous discussions:

- 2021, 356 comments: https://news.ycombinator.com/item?id=29125934

- 2018, 608 comments: https://news.ycombinator.com/item?id=16806114

I'm sure there are others, but the fact that the same document can be found through various paths (without www domain, without /drafts/ path, or without /matrix/ path) makes it harder to find previous postings.

Re: Why SQLite does not use Git (2018)

#23
post #6

I think the explanation does not make any sense in 2023, if 99.99% of dev use Git you have to use Git, using your own solution that no one else uses or know or need to know is bad. If you want to make your project more open to contribution you have to use what the rest of the industry is using. Edit: After reading some responses, I'm really surprised that sqlite does not accept contributions.

The average contribution via something like github is just a waste of time, especially if a project is popular having many users.

Re: Why SQLite does not use Git (2018)

#25
post #7

I think there are some legitimate criticisms of Git here. But some of them are...odd. Despite using Git in a variety of circumstances, from a local personal repo project to very large company repos, I admit I haven't run into about half of these issues. > The closest I have found is the network, which is slow to render (unless it is already cached), does not offer nearly as much details, and scarcely works at all on…

All the time. I would say at least 50% of my code browsing is done from my phone. I make heavy use of the mobile GitHub web interface for this (find-references support has been a godsend, search is still meh, I hate how they keep breaking basic find-in-page with SPA jank). Also Searchfox [0] when I need to comb through Firefox code (fast, excellent, no complaints—well, I guess blame on mobile could be better).

Context: grad student, programming languages and systems research plus a bunch of IoT hacking on my own time. Either elder Gen Z or youngest possible Millennial, depending where you put the cutoff.

[0] https://searchfox.org

Re: Why SQLite does not use Git (2018)

#26

https://git-man-page-generator.lokaltog.net is the funniest thing I've seen in a while

> git-erase-working-treeshould be used when you want to cautiously erase the current working tree of an upstream root and the config, and want to quiltimport to a active GUI.

sounds useful!

Re: Why SQLite does not use Git (2018)

#27
post #7

I think there are some legitimate criticisms of Git here. But some of them are...odd. Despite using Git in a variety of circumstances, from a local personal repo project to very large company repos, I admit I haven't run into about half of these issues. > The closest I have found is the network, which is slow to render (unless it is already cached), does not offer nearly as much details, and scarcely works at all on…

Well, I'm using git to manage my blog. I wrote an Android editor to edit on GitHub and then modified it to work on gitlab. There are lots of reasons but mostly it is because git is impossible to use on mobile, regardless of whether you are using GitHub or gitlab. Checking status is possible but barely anything beyond that.

This write-up really resonated with me in other ways. I wrote a book for O'Reilly about GitHub and still can't wrap my head around git after more than ten years of using it. The points made here resonate with me.

Re: Why SQLite does not use Git (2018)

#28
post #7

I think there are some legitimate criticisms of Git here. But some of them are...odd. Despite using Git in a variety of circumstances, from a local personal repo project to very large company repos, I admit I haven't run into about half of these issues. > The closest I have found is the network, which is slow to render (unless it is already cached), does not offer nearly as much details, and scarcely works at all on…

I've tried to extend my work day by checking on projects from the train. Absent spotty data coverage, I've found GitHub works fine and I can do light code reviews easily.

GitHub pulse[1] is a great UI for looking at recent activity. This page is bare for the SQLite mirror because they don't work on GitHub so it only has commit history. The linked Caddy project is a better example. IMO it looks more useful than the timeline.

I wonder if anyone's built the equivalent view for git/GitHub already. Shouldn't be too difficult.

[1] https://github.com/caddyserver/caddy/pulse

Re: Why SQLite does not use Git (2018)

#30

I'm glad Fossil works for them, but this line is bothered me: > In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. That one binary contains all the functionality of core Git and also GitHub and/or GitLab. It manages a community server with wiki, bug tracking, and forums, provides packaged downloads for consumers, login managements, and so forth, with no extra software require…

From an ABI perspective, there's not a huge difference, mostly just where the code resides on disk, all local or scattered across multiple inodes.
Post reply on HN