<story><title>Microsoft acquires Citus Data (YC S11)</title><url>https://blogs.microsoft.com/blog/2019/01/24/microsoft-acquires-citus-data-re-affirming-its-commitment-to-open-source-and-accelerating-azure-postgresql-performance-and-scale/</url></story><parent_chain><item><author>ABeeSea</author><text>If the creators of Postgres wanted all improvements to be upstreamed, they wouldn’t have released under a permissive license. The ability to use Postgres commercially without exposing your entire codebase to copyleft risk is one of the reasons it’s used commercially in the first place.</text></item><item><author>cdbattags</author><text>In the latest world of Postgres:&lt;p&gt;- we now have closed source Amazon Aurora infrastructure that boasts performance gains that might never see it back upstream (who knows if it&amp;#x27;s just hardware or software or what behind the scenes here)&lt;p&gt;- we now have Amazon DocumentDB that is a closed source MongoDB-like scripting interface with Postgres under the hood&lt;p&gt;- lastly, with this news, looks like Microsoft is now doubling down on the same strategy to build out infrastructure and _possibly_ closed source &amp;quot;forked&amp;quot; wins on top of the beautiful open source world that is Postgres&lt;p&gt;Please, please, please let&amp;#x27;s be sure to upstream! I love the cloud but when I go to &amp;quot;snapshot&amp;quot; and &amp;quot;restore&amp;quot; my PG DB I want a little transparency how y&amp;#x27;all are doing this. Same with DocumentDB; I&amp;#x27;d love an article of how they are using JSONB indices at this supposed scale! Not trying to throw shade; just raising my eyebrows a little.</text></item></parent_chain><comment><author>basilgohar</author><text>This is a big assumption.  There are many reasons to release something as copyleft – not everyone that releases BSD-like is actively choosing to deprioritize upstreaming.  Rather, they are choosing a license that is less restrictive which has other advantages beyond non-copyleft.&lt;p&gt;Moreover, using copyleft software doesn&amp;#x27;t mean &lt;i&gt;using&lt;/i&gt; forces you to release code.  There are specific interactions that trigger the sharing clause in, for example, the GPL, such as distribution, linking, and so on.  There remain many, many uses that allow commercialization that do not run afoul of the copyleft nature of the GPL.&lt;p&gt;I am commenting because I have seen this sentiment repeated ad nauseum on here and, maybe that&amp;#x27;s not what you meant, but I felt the need to clarify.  Moreover, if the code is not AGPL, most online uses do not run afoul, because the code product (say executables) are not themselves being distributed.  AGPL was formulated to close this loophole, but GPL code is free from this.</text></comment>
<story><title>Microsoft acquires Citus Data (YC S11)</title><url>https://blogs.microsoft.com/blog/2019/01/24/microsoft-acquires-citus-data-re-affirming-its-commitment-to-open-source-and-accelerating-azure-postgresql-performance-and-scale/</url></story><parent_chain><item><author>ABeeSea</author><text>If the creators of Postgres wanted all improvements to be upstreamed, they wouldn’t have released under a permissive license. The ability to use Postgres commercially without exposing your entire codebase to copyleft risk is one of the reasons it’s used commercially in the first place.</text></item><item><author>cdbattags</author><text>In the latest world of Postgres:&lt;p&gt;- we now have closed source Amazon Aurora infrastructure that boasts performance gains that might never see it back upstream (who knows if it&amp;#x27;s just hardware or software or what behind the scenes here)&lt;p&gt;- we now have Amazon DocumentDB that is a closed source MongoDB-like scripting interface with Postgres under the hood&lt;p&gt;- lastly, with this news, looks like Microsoft is now doubling down on the same strategy to build out infrastructure and _possibly_ closed source &amp;quot;forked&amp;quot; wins on top of the beautiful open source world that is Postgres&lt;p&gt;Please, please, please let&amp;#x27;s be sure to upstream! I love the cloud but when I go to &amp;quot;snapshot&amp;quot; and &amp;quot;restore&amp;quot; my PG DB I want a little transparency how y&amp;#x27;all are doing this. Same with DocumentDB; I&amp;#x27;d love an article of how they are using JSONB indices at this supposed scale! Not trying to throw shade; just raising my eyebrows a little.</text></item></parent_chain><comment><author>cdbattags</author><text>100% agree. I&amp;#x27;m just weary of all these &amp;quot;mini optimizations&amp;quot; that all these cloud providers are about to start doing differently.</text></comment>