Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why SQLite does not use Git (2018)

sqlite.org

Post reply on HN
Print view View original

11–20 of 454 posts

Re: Why SQLite does not use Git (2018)

#11

Post by enigmurl »

Thaxll wrote: 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.

Sure, but with that kind of argument will we ever be able to make the switch to a better vcs if one exists? You have to start somewhere.

Re: Why SQLite does not use Git (2018)

#12

Post by casion »

Thaxll wrote: 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.

> If you want to make your project more open to contribution

This is a key point, and assuming this in the positive is often a mistake. Not all projects want, or can handle, increased contribution.

Re: Why SQLite does not use Git (2018)

#13

Post by upon_drumhead »

Thaxll wrote: 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.

> If you want to make your project more open to contribution you have to use what the rest of the industry is using.

They don't want contributions

https://www.sqlite.org/copyright.html

> In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.

Re: Why SQLite does not use Git (2018)

#14

Post by eska »

Thaxll wrote: 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.

Says who?

Re: Why SQLite does not use Git (2018)

#15

Post by grayhatter »

casion wrote: post #12
Thaxll wrote: 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.

> If you want to make your project more open to contribution This is a key point, and assuming this in the positive is often a mistake. Not all projects want, or can handle, increased contribution.

sqlite is actually a perfect example of a project that specifically excludes public code contribution.

https://www.sqlite.org/copyright.html

Re: Why SQLite does not use Git (2018)

#16

Post by eska »

upon_drumhead wrote: post #13
Thaxll wrote: 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.

> If you want to make your project more open to contribution you have to use what the rest of the industry is using. They don't want contributions https://www.sqlite.org/copyright.html > In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.

> from people who have not submitted an affidavit dedicating their contribution into the public domain.

Don’t spread FUD

Re: Why SQLite does not use Git (2018)

#17

Post by samspenc »

Thaxll wrote: 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.

I upvoted the post since I think it's a overall interesting technical discussion of git's downsides and some fossil upsides.

But my response would be the same as what I argue in these React or other "popular-vs-other-frameworks" discussions that come: the alternatives may be better, faster, easier etc - BUT:

  - The popular solution has the larger ecosystem, and there are more existing plugins or modules you can plug-and-play instead of having to build out your own solution for.
  - If you hit any edge case or obscure issues with the popular framework, someone somewhere on the Internet has hit it and it's likely a QA on Stackoverflow / Reddit and similar (and hence ChatGPT and other LLMs as a result)
  - People understand the popular solution more in depth and it's easier to learn about the architecture as well as its pros and cons.

Re: Why SQLite does not use Git (2018)

#18

Post by qaq »

BuckRogers wrote: post #8

I’m sure git is less than ideal. I pretty much just know enough to do what I need to do with it. The only reason I want to use it is because it is the industry standard tool. Otherwise Hg, Perforce, have all had pretty compelling arguments put forward for their use. There’s so much technical churn in this industry, that any time I can use something that’s widely embraced I’m actually happy for that. Regardless of my…

I'd choose git over perforce any day.

Re: Why SQLite does not use Git (2018)

#19

Post by upon_drumhead »

eska wrote: post #16
upon_drumhead wrote: post #13

Earlier quoted context omitted.

> If you want to make your project more open to contribution you have to use what the rest of the industry is using. They don't want contributions https://www.sqlite.org/copyright.html > In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches.

> from people who have not submitted an affidavit dedicating their contribution into the public domain. Don’t spread FUD

Here you go.

https://sqlite.org/forum/forumpost/860f855ed144703d

> The project requires a document on file but it doesn't accept that document from arbitrary people. It's effectively "by invitation only" and Richard hands out those invitations at his sole discretion.

Post reply on HN