Have pgrust folks reconsidered this? Else, IMO we can have an independant rust port of pgrust, which can be MIT, which will garner more attention.
For instance, Mongo, Cockroach, and Materialize have all gone source available. We picked AGPL because it's the best balance between open source and prevents Amazon from just repackaging it and selling it.
If AGPL is an issue for anyone, we would be happy to dual-license under a commercial license.
Will await a MIT based fork myself.
AGPL is untested in courts. There is no definitive definition of what could be considered within the blast radius such that it would require AGPL licensing.
There's a reason AGPL is banned at Google and most sane companies. It's simply too dangerous.
You can't simply say "clients aren't bound" because it depends.
I'd rather see the BSL used here to be perfectly honest. At least it's simple.
I consider AGPL a poison pill in my work. That is not true with a suitable commercial license, although I expect a lot more commercial product (support/features/etc). As you note, your objective is to prevent commercialization of your software, but radically speeding up analytics is primarily a concern of large organizations so it seems like a mismatch in purpose.
That's up to GCP then. I'm sure OP would be willing to license pgrust to them for an appropriate price.
Also, from the trajectory of the project it doesn't look like they are significantly deoendent on outside code contributions.
You should be setting up a CLA process then ASAP if you are looking to take outside contributions.
It’s weird because those who actually care about optimized pg gains are most likely large corporate customers. Why make a product targeting them and license it in such a way they’ll never use it?
This also hard blocks upstreaming any beneficial features into core Postgres.
I doubt even 30000x faster would prompt a policy change.
> light-years away from what happened here
There is also zero evidence a human has reviewed a meaningful amount of the code generated for the port, let alone the original C code from Postgres, given the size/scale of the project and the how quickly it was produced.
Also, you can successfully sell a systems project that is only 10% faster. 30000x faster and they are throwing illegal and debauched things through your window to get access to your improvements.
What does it being system code have to do with anything?
Most systems code has to be "canonical". That means it can't be improved. Imagine the most difficult PR review you have ever had. Now give the reviewers OCD and an extra 30 IQ points. And every single code change has to live up to this standard. That's what it has to do with this.
You didn't express anything unique to systems engineering.
[0]: With Exhibit B, which prevents relicensing to GPL. It is also analogous to CDDL.
PS Learn how DBs do joins for more information. Specifically the differences between hash joins, merge joins and nested loop joins. They are basically fancy ways to page part of your working set to disk at huge performance penalties.
PPS As memory gets more expensive, these techniques get more valuable. When it gets cheap, they lose value.
Yes, at [tech corp dayjob], any dependency is likely to be banned for arbitrary reasons if you bring it to the attention of the wrong people. It doesn't have to go against any of our policies e.g. don't mention anything with GPL in the name around the "risk" people. In fact, do not ever talk to the "risk" people and hope they don't talk to you.
Latest news: Apparently, devtools are a legal risk. Basic reverse-engineering of client-side JS is now banned.
The delusions really seem to scale with headcount.
Wait, sorry, you're asking why make something enterprise customers might pay for, and then not give it away to them for free?
You are free to volunteer your time to Amazon, no one is stopping you. They would probably accept cash donations as well.
It's not insurmountable. Lots of companies have been built on AGPL or adjacent licenses. It's just a meaningful hurdle. People can do whatever they want, your framing of "oh just give your money to corporations" is ridiculous as I'm not advocating for anyting like that.
What we don’t know for sure is whether there is any copyright for LLM-generated code. The license might be irrelevant!
Just look at Garry Tans ai slop prompts which got 60k stars in a few weeks.
hey claude, do a breakthrough
You can find the actual git history at the v0.2 github tag.
Co-Authored-By: Fable <noreply@anthropic.com>
It's easy to claim AI slop nowadays, but you should still mistrust-but-verify.
> "do a breakthrough and find a structured counterexample"
We're literally talking about an "X but in Rust" project already...