Live data from Hacker News

Why SQLite does not use Git (2018)

sqlite.org

241–250 of 454 posts

Re: Why SQLite does not use Git (2018)

#241

Earlier quoted context omitted.

Git actually is bundling a lot of stuff you probably don't realize. Run 'git instaweb' for example and it will spin up a local CGI server and perl CGI script to give a very simple web UI: https://git-scm.com/docs/git-instaweb Fossil isn't much different in core functionality here. There is a ton of email client integration and functionality in git too that most people who only use GitHub probably have absolutely no i…

> Run 'git instaweb' for example and it will spin up a local CGI server and perl CGI script to give a very simple web UI: ~ $ git instaweb fatal: git was built without support for git-instaweb (NO_PERL=YesPlease).

on Ubuntu 22.04.2 LTS

lighttpd not found. Install lighttpd or use --httpd to specify another httpd daemon.

Re: Why SQLite does not use Git (2018)

#242

[flagged]

> It’s easy one of the most powerful, flexible, Probably, yeah. > and if you take the time to learn it, SIMPLE models for version control. ... And there it all falls apart. In practice, git requires a massive amount of learning to use competently, to the point that using something else just to avoid the learning curve is fairly reasonable.

As someone who has learned the ins and outs of git, I struggle to think of a better model for revision control. I never have issues with it anymore, and it took maybe a day to learn how it works under the hood. There's a great article on git internals directly in the git manpages.

Re: Why SQLite does not use Git (2018)

#243
I've been getting the hang of darcs recently. There's been your typical hiccups of learning something new, but it’s been an interesting process. I wouldn’t be surprised to see a Patch Theory-based DVCS be the Git successor, & if true, darcs will be the early inspiration and the terminology would likely be copied from darcs when in doubt so it doesn’t feel like a waste to learn. It’s definitely not a beta software supporting all the necessary basics for DVCS. Considering my biggest gripe is reliance on a Haskell module for SSH that doesn’t support ed25519 keys, there aren’t many issues.

Re: Why SQLite does not use Git (2018)

#244
post #220

Earlier quoted context omitted.

Git BASH (from that page) is what they referred to when they said "you literally have to bring half of a whole unix with you to run git".

GitBash, AutoHotkey, Notepad++, 7zip and PowerToys are the basic installs I do on any Windows I am given. Any dev opening a CMD is suspect, to me.

Not for me, as Windows developers don't need to depend on UNIX culture.

The only thing that is debatable is using command prompt instead of powershell, unless for legacy scripts.

Re: Why SQLite does not use Git (2018)

#245
post #180

Earlier quoted context omitted.

git...is difficult to install? What's difficult about apt-get install git?

For what it’s worth, on windows without wsl you literally have to bring half of a whole unix with you to run git.

thb that "half of a unix" usually weights less than some other popular runtime envs

Re: Why SQLite does not use Git (2018)

#246
> In contrast, Fossil is a single standalone binary which is installed by putting it on $PATH. ... It manages a community server with wiki, bug tracking, and forums, provides packaged ... Standing up a community server for Fossil takes minutes.

Let's see...

About a year ago I try to set up fossil because I wanted the issue tracking it supposedly provides. I'm already using git for VC and will stick with it.

Spend several hours and got nowhere. It's a local web-based thing and all I kept getting back was 404 Not Found. Did some reading around, found somebody had solved the problem by using --force option (IIRC, to force creation of a repo) but that didn't get me to anything actually working. The docs were unhelpful, as in wrong. Gave up. If you can't document your software then don't release it. Certainly don't make claims for its greatness and ease if you ignore what your users are saying on your message boards.

Re: Why SQLite does not use Git (2018)

#247
post #199

Earlier quoted context omitted.

Let's not forget how long it even took for there to be a reasonable Windows build of git. Git implicitly relied on significant amounts of Linux tooling which required bringing over an entire Mingw environment.

>lets not forget I'd gladly take a FOSS Visual Studio on Linux. Heck, I won't even hold a grudge if it's under 60MB. Promise.

60megs?

that'll bareley hold the latest styling theme package thingy

Re: Why SQLite does not use Git (2018)

#248
post #47
post #42

Earlier quoted context omitted.

> git, for all its issues, is not bundling the kitchen sink. It doesn't bundle the kitchen sink in its native *nix environment, but for Windows it does. Git installer is > 50 MB, including (if I remember correctly) even a terminal. While you can download Fossil as a 3.3 MB standalone binary for any supported platform.

I don’t develop on a machine where this matters, even at scale. Who cares about a 47MB difference on machines with a few gigs of ram?

for scale you usally want things to be efficient. and caring about caching effects is not seldomly the lowest hanging fruit.

Re: Why SQLite does not use Git (2018)

#249

Earlier quoted context omitted.

Git actually is bundling a lot of stuff you probably don't realize. Run 'git instaweb' for example and it will spin up a local CGI server and perl CGI script to give a very simple web UI: https://git-scm.com/docs/git-instaweb Fossil isn't much different in core functionality here. There is a ton of email client integration and functionality in git too that most people who only use GitHub probably have absolutely no i…

I tried that (primarily because I didn't know about it and was excited), but it didn't work. It needs me to install "lighttpd" to work. And the steps to install that are not straightforward. I like that a lot of functionality is not bundled up in the git that I have already installed in my computer, but at the same time, I agree with the fact that adding these separate binaries is not easy as a user.

> lighttpd

Wow now that's a blast from the past. That's a nice relic from the times of people getting annoyed with Apache's one process per request model and Nginx not being popular just yet. Does anyone use that anymore for, well, anything?

Re: Why SQLite does not use Git (2018)

#250

>Git focuses on individual branches, because that is exactly what you want for a highly-distributed bazaar-style project such as Linux. Linus Torvalds does not want to see every check-in by every contributor to Linux: such extreme visibility does not scale well. Contrast Fossil, which was written for the cathedral-style SQLite project and its handful of active committers Ugh...so after all that fanfare of how amazing…

Personally I see "doesn't scale well" as a feature, if I'm evaluating something to use on a personal or small project. Tools with clear limits on what they're not for usually have a more polished experience for what they are for.

In that case you might really love "...SCons, a popular Python-based build tool. In a nutshell, my experiments showed that SCons exhibits roughly quadratic growth in build runtimes as the number of targets increases" [0]

[0] https://blog.melski.net/2013/12/11/update-scons-is-still-rea...

Post reply on HN