5 ms·

I like it. I totally get the problem projects like mongo, redis and sentry face. AWS, azure etc just eat their lunch and don’t help anybody. That will kill ope

I like it. I totally get the problem projects like mongo, redis and sentry face. AWS, azure etc just eat their lunch and don’t help anybody. That will kill open source in the long run. This still gives me access to inspect the code, contribute fixes I might want, self host if I feel like it or pay someone for the SaaS if I don’t, knowing the money goes to someone who contributes to the project. And if the original authors bork the product and after two years it becomes clear they won’t fix their ways, I can fork the old product code I liked and develop it into the product I want. Heck if I’m right and my idea is better than the original I’ll eat their lunch too.

pjmlp 3y ago
What we have now is exactly what would have happened if the AT&T vs BSD lawsuit had come to a conclusion before Linux kernel came into the scene. Big iron UNIX would keep going and cherry picking from the BSDs as it had done until the lawsuit took place. It is no surprise that all new FOSS OSes for IoT, none of them embrace copyleft licenses.
0xDEF 3y ago
>AWS, azure etc just eat their lunch and don’t help anybody I know that AWS made a blatant hosted version of Elasticsearch without contributing back but the other examples are less damning. Azure's MongoDB offering is just the MongoDB API on top of their own document-oriented storage and querying architecture. Their globally scalable Redis offering is most likely also their own implementation and only using the same API as Redis.
geerlingguy 3y ago
Two years is like 20 years in most software ecosystems. If a JS library or mobile front end used this license, by two years the underlying tech that old version used would all be extinct.
- ic_fly2 3y ago
  You’re not going to need this for a js library that doesn’t have a saas component.
- IshKebab 3y ago
  No it isn't. 2 years is very recent in most software ecosystems. Even in the JS world it is really very recent, depending on the software. E.g. 2 year old Bootstrap is perfectly fine. 2 years seems hilariously short for me. If AWS want to rip this off they'll be very happy to use code that is only 2 years old to do it. Or fork a 2 year old version and reimplement only 2 years of work. 4 years makes way more sense, and even that is quite generous IMO.

pjmlp 3y ago

What we have now is exactly what would have happened if the AT&T vs BSD lawsuit had come to a conclusion before Linux kernel came into the scene. Big iron UNIX would keep going and cherry picking from the BSDs as it had done until the lawsuit took place. It is no surprise that all new FOSS OSes for IoT, none of them embrace copyleft licenses.

0xDEF 3y ago

>AWS, azure etc just eat their lunch and don’t help anybody I know that AWS made a blatant hosted version of Elasticsearch without contributing back but the other examples are less damning. Azure's MongoDB offering is just the MongoDB API on top of their own document-oriented storage and querying architecture. Their globally scalable Redis offering is most likely also their own implementation and only using the same API as Redis.

geerlingguy 3y ago

Two years is like 20 years in most software ecosystems. If a JS library or mobile front end used this license, by two years the underlying tech that old version used would all be extinct.

ic_fly2 3y ago
You’re not going to need this for a js library that doesn’t have a saas component.
IshKebab 3y ago
No it isn't. 2 years is very recent in most software ecosystems. Even in the JS world it is really very recent, depending on the software. E.g. 2 year old Bootstrap is perfectly fine. 2 years seems hilariously short for me. If AWS want to rip this off they'll be very happy to use code that is only 2 years old to do it. Or fork a 2 year old version and reimplement only 2 years of work. 4 years makes way more sense, and even that is quite generous IMO.