It's interesting to compare the revenue model of Curl to SQLite.

Both are permissively licensed.

Both are embedded in billions of offerings.

Both launched around the same time.

SQLite has built a multi-million dollar annual business supporting it, while Curl I believe has not.

> SQLite has built a multi-million dollar annual business supporting it, while Curl I believe has not.

Curl's founder works for a small American company called WolfSSL. AFAIK he works on Curl-related stuff full time.

Didn’t Mozilla also used to fund him?

That's true for many DBs, but how much maintenance did you have to perform on the dozens of SQLite databases living in your phone and your $HOME?

It may not be me, but someone has to maintain those databases unless the software that uses it stops changing. Where curl has to maintain compatibility with every call to curl, I would wager that sqlite has to maintain compatibility with a larger surface area of APIs.

HTTP regularly changes. 2 and 3 are very big enhancements for some use cases.

Maybe read what SQLite is first

> SQLite has built a multi-million dollar annual business ...

Interesting, where'd you hear that? :)

Haven't heard figures regarding SQLite's business side of things (yet), and doing some online searching isn't turning up anything useful.

Your challenge piqued my curiosity. ;)

SQLite sells support, licensing, and services using a small staff of engineers. See https://sqlite.org/prosupport.html The premium support contract is $120k/year, and it appears from the website that they have at least 4 such clients. See https://www.sqlite.org/index.html#consortium_members But even if those are all past clients, all things considered--support tiers, US domestic engineering staff, etc--it seems likely their annual revenue is at least $500K, and would not be surprising if more than $2M.

It would be interesting to hear concrete sources, though.

The SQLite Consortium clearly has enough employees and importance that that's a fair estimate. You could talk to them about joining the consortium and see if you can manage to get a quote, then extrapolate from that, but really, the members are deep pocket types who are utterly dependent on SQLite3 and who want improvements (not just support).

It also looks like the Ruby GEM has a resource leak with it :) (or it doesn't terminate the connection? The server is timing out saying the full body has not been read).

Curl 8 got pulled into a base image update to Alpine Linux.

Which gem? There are several that bind against libcurl.

I use Typhoeus which uses Ethon depends on ffi. Crash happens. Sorry English is not my mother language.

I'll have to check when I get into work.

I didn't realize curb was still maintained. Would be helpful to report the issue here: https://github.com/taf2/curb/issues

Yeah, I was/am planning to do that. But... the project giving us trouble is still on 0.9.11 and another project that is on latest doesn't seem to be having the same issue, so some more testing is needed. At the moment, we're going to rebuild using the older base image and then we'll upgrade the gem and test this sprint.

Update: Latest gem still has the elevated error rates from the service we're connecting to but NOT the resource leak.

Anyone know if this fixes slow SFTP? ie https://daniel.haxx.se/blog/2014/05/14/why-sftp-is-still-slo...

Ain't nothing wrong with a little unencrypted HTTP between friends. In your localhost.

I mean, as long as all of them are consenting adults...

Yes, I'm sure our static public images transferred from static web server to caching proxy need that extra protection /s

You mean for testing, or in general?

I would rather use the same protocol for testing that I use for higher environments, unless there is a strong reason not to. Same reason I wouldn't use SQlite locally and postgres in staging / prod.

Daniel has no "prod" or "testing" environments. Not every dogma needs to be applied for everything, everywhere.