21–30 of 99 posts
Earlier quoted context omitted.
What's the difference between community and commercial customers, aside from support? Is InnoDB a feature? Why would MyISAM support be free but InnoDB support have a yearly fee?
MySQL is dual-licensed. If you download the community server, it's GPL licensed. If you want to distribute MySQL as part of your application, then your application may have to be GPL licensed as well, which is often undesirable. ISVs and others that need to distribute MySQL can buy one of the commercial editions to get it under a non-GPL license. If you're worried about the future, Oracle agreed to maintain the dual-…
Even the $10,000 cluster edition (which is based on NDB) is GPL. So clearly they can not be selling software, I can only assume these are prices for support, not for software. Have they taken down download links? Removed source code?
GPL doesn’t mean you can’t sell it; it means you have to provide source and allow derivative products within the constraints of the license.
Edit: I guess I can see how you can read it in reverse from what I meant.
[deleted]
How is this different than before? MySQL was always a dual-license product. You can use the product if you comply with the terms of the GPL, or purchase a commercial license to get priority features, priority support, and get around the GPL terms. This is the same business model that MySQL AB and Sun have used for the last decade.
Earlier quoted context omitted.
What's the difference between community and commercial customers, aside from support? Is InnoDB a feature? Why would MyISAM support be free but InnoDB support have a yearly fee?
MySQL is dual-licensed. If you download the community server, it's GPL licensed. If you want to distribute MySQL as part of your application, then your application may have to be GPL licensed as well, which is often undesirable. ISVs and others that need to distribute MySQL can buy one of the commercial editions to get it under a non-GPL license. If you're worried about the future, Oracle agreed to maintain the dual-…
The FSF call it "mere aggregation": http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
Business first, not the heart and minds of developers.
Luckily the 'L' + 'A' + 'P' cannot be bought.
LAPP stack anyone?
Earlier quoted context omitted.
MySQL is dual-licensed. If you download the community server, it's GPL licensed. If you want to distribute MySQL as part of your application, then your application may have to be GPL licensed as well, which is often undesirable. ISVs and others that need to distribute MySQL can buy one of the commercial editions to get it under a non-GPL license. If you're worried about the future, Oracle agreed to maintain the dual-…
How exactly does distributing MySQL as part of your application make your application GPL as well? It's not a retorical question, can you please suggest a case? Unless you outright fork MySQL to make your own database, you can run and distribute it with your proprietary stack without being forced to license your code as GPL. The FSF call it "mere aggregation": http://www.gnu.org/licenses/gpl-faq.html#MereAggregation
You have got to admire the evil villany we're up against. Buying the 'M' in LAMP and then exploiting that position. Business first, not the heart and minds of developers. Luckily the 'L' + 'A' + 'P' cannot be bought. LAPP stack anyone?
Unless P=Python? :-)
LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".