MySQL and SCO Join Forces
matchboy writes "CNET is reporting that MySQL and SCO have signed a partnership to work on "joint certification, marketing, sales, training and business development work for a version of the database for SCO's new OpenServer 6 version of Unix." Why would MySQL decide to work directly with a company that has deemed the GPL as unconstitutional?"
Dollars always trumps the Constitution. Haven't you been paying attention to recent politics?
Reminder: Apple owns 1/255th of the internet.
Why would MySQL decide to work directly with a company that has deemed the GPL as unconstitutional?"
...because MySQL stands to make money off of this?
I dunno...just a guess.
Slashdot: Where people pretend to be twice as smart as they really are by behaving like children.
they risk a large-scale negative reaction in order to attempt a push into a small, dying market niche.
as i have pointed out on groklaw, the companies running dbms on their unixware/openserver boxes will likely stick with their dbms when they move to another *nix.
companies hate switching dbms because it can get very messy very fast.
sum.zero
Who cares? MySQL is one of the few open source companies that seems to be making the headlines doing business in the real world! Good for them!
Going into partnership with SCO just after Novell has applied to freeze their funds with the intention of pillaging them via the courts is not the brightest of ideas.
Hmmmmmm..... Deep fried and look like Squirrel.
And one thing businesses do is make money.
One of the ways businesses make money is by offering goods or services.
Some of the goods and services MySQL AB has offered in the past include:
I haven't followed MySQL in awhile, but it seems like SCO is actually just buying into some kind of reseller program MySQL AB is offering and calling it a partnership, which is kind of like buying some routers from Cisco and saying Cisco is your business partner.
If someone walks into your store and tries to buy something, are you going to say no?
Some people do it for the principle of the thing. That's a big Open Source mentality, where have you been?
Yes, I am a smart ass; it's better than the alternative.
> > ... rather, it forces proprietary developers to use MySQL under the proprietary license.
> Nothing forces anybody to do anything.
I see you are intentionally misinterpretting my words. So, here is the long version:
It [the GPL + proprietary licensing scheme] forces proprietary developers, if they want to include MySQL in their application, and if they don't want to GPL their own application, to use MySQL under the proprietary license.
> So by your logic, the GPL license forces proprietary developers to ignore the product altogether?
Of course -- unless they are prepared to GPL their own code. That's what the license says. Or are you saying that no one is "forcing" them to obey the license?
> More license options means more choice, and choice is *good*.
What crap. You are intentionally misrepresenting the situation.
The dual licensing scheme used by MySQL and Trolltech _removes_ choice. It removes the choice of proprietary developers to use MySQL and Qt under an Open Source license. The LGPL license would have given them that choice.
Let's see what Richard Stallman had to say on this topic:
"Using the ordinary GPL for a library gives free software developers an advantage over proprietary developers: a library that they can use, while proprietary developers cannot use it."
"Using the ordinary GPL is not advantageous for every library. There are reasons that can make it better to use the Library GPL in certain cases. The most common case is when a free library's features are readily available for proprietary software through other alternative libraries. In that case, the library cannot give free software any particular advantage, so it is better to use the Library GPL for that library."
"This is why we used the Library GPL for the GNU C library. After all, there are plenty of other C libraries; using the GPL for ours would have driven proprietary software developers to use another--no problem for them, only for us."
MySQL and Qt are available under proprietary licenses. Therefore, rather than GPLing their own code, proprietary developers will simply use the proprietary license.
In other words, MySQL's and Trolltech's use of the GPL, instead of the LGPL, produces exactly the opposite effect to what Stallman prefers. The dual licensing scheme, rather than increasing the amount of Free software, simply encourages proprietary developers to use the proprietary versions of the libraries.
> This is like the argument against the BSD license: but... but... someone could develop their own closed source app!
That statement is completely illogical. It does not follow from what I wrote.
I am concerned about people who choose to run applications A, B, and C, becoming locked in to the underlying middleware, without realizing it. It happened before with Windows, and it could happen again with MySQL and Qt.
What you are saying is the exact opposite to what I wrote. I said that they should have used the _LGPL_, which _allows_ proprietary developers to use the code.
The advantage for the rest of us is that anyone who uses those proprietary applications are only locked in to those applications. What they avoid is the _Network Lock-in_ to the underlying middleware, which is much worse.
As to your last paragraph, I have no idea what it has to do with my original post.
I am advocating for people to be careful about the software they use, and to think about the long-term effects of the licenses for that software.
If you call that trolling, then I have to wonder what your agenda is.