News for hackers. Stuff that matters.
Re:Why SQLite Does Not Use Git by 1vuio0pswjnm7 on Sunday July 23, 2023 @04:15AM (#36833485)
Full quote:

"Git is complex software. One needs an installer of some kind to put Git on a developer workstation, or to upgrade to a newer version of Git. Standing up a Git server is non-trivial, and so most developers use a third-party service such as GitHub or GitLab, and thus introduce additional dependencies.

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. Standing up a community server for Fossil takes minutes. And Fossil is efficient. A Fossil server will run fine on a $5/month VPS or a Raspberry Pi, whereas GitLab and similar require beefier hardware.

Less administration means that programmers spend more time working on the software (SQLite in this case) and less time fussing with the version control system."

In 2018, git bundled perl libraries by default and required a perl installation of at least 5.8. This could be disabled by compiling with NO_PERL. Another dependency was tcl/tk wish. This could be disabled by compiling with NO_TCLTK

In contrast, fossil uses tcl instead of perl and comes bundled with a boostrapping jim tcl interpreter contained in a single 588k .c file.

Like fossil, git does include both client and server, i.e., git-daemon. Yet it seems like most git users rely on Github or some other third party for the server.

There are no comments on this comment yet.