MySQL CEO Insists He's Not Supping With The Devil 197
jg21 writes "In the continuing saga of the decision by MySQL previously discussed here on Slashdot to make a deal with SCO Group, the company's CEO Marten Mickos has now granted an interview in which he addresses the inevitable criticism that the deal has provoked in the F/OSS community. His main defense seems to be that other companies have ported to SCO too. He admits money too played a part." From the article: "We believe that porting a GPL version of MySQL for the SCO OpenServer platform gives thousands of users more options when it comes to choosing a database -- which is a good thing. The deal produces revenue for us and this allows us to hire more open
source developers. We didn't make the decision lightly; we knew SCO was a sensitive subject with the free software and open source communities."
Not So Free Software (Score:4, Interesting)
Re:Not So Free Software (Score:2, Insightful)
Re:Not So Free Software (Score:2)
The company who develops that platform intends to destroy one of the other platforms you sell your sotfware for. That's why it's an issue.
Re:Not So Free Software (Score:3, Insightful)
Re:Not So Free Software (Score:3, Insightful)
Re:Not So Free Software (Score:2)
Re:Not So Free Software (Score:2)
Re:Not So Free Software (Score:5, Interesting)
The only reason it's an issue is because web sites like this one are heavily infiltrated by astro-turfers that will try to make it an issue so their masters can then squeal about 'linux zealots.'
MySQL made a deal, they got paid money to support a platform. That the client, in this case, happens to be the litigiousbastards [sco.com] was sure to raise a few eyebrows, and did, but not much more than that. Business is business. I hope Mårten made sure their check cleared before he let anyone put in any hours on that project... *shrug*
Re:Not So Free Software (Score:3, Funny)
Re:Not So Free Software (Score:2)
I hope MySQLs "Prepaid Legal" is current!
Re:Not So Free Software (Score:2)
That's funny, because I actually know a few 'linux zealots' and some of them really do say things like that. Now it may be that there really are a few people paid/encouraged to come here and act up, but I think it's much more likely that actually, most of the people acting like that just are like that. It would cert
Re:Not So Free Software (Score:3, Insightful)
This being said, I think that Mickos came across very well in this interview. He did exactly what the company should have done from the beginning which is to say indicate that this is just about bringing MySQl to more customers.
My prior concerns had more to do with other public comments than with with the SCO partnership per se.
Re:Not So Free Software (Score:2)
Paranoid? Yes, but this is SCO and all the people they sued so far were Openserver customers switching to Linux. What was the deal anyway between mysql and sco? Did sco get some special IP sharing agreement? How do I know?
Re:Not So Free Software (Score:5, Funny)
My favorite claim they made was when they claimed that Daimler Crysler did not adequately provide a list of systems running their software, and that the response of "we haven't used your software in seven years" did not qualify as a list.
Fortunately the judge was not amused by the level of creativity in this interpretation and promptly threw out most of the SCO v. DCC suit (she left the possibility that SCO could sue DCC for not responding in a timely fashion to their inquiry, but the rest was thrown out).
Porting is NOT the issue (Score:2)
The issue is that MySQL AB has now partnered with The SCO Group.
Yes, they've tried to be as arm's-length about it as possible (and who wouldn't?), but MySQL AB didn't need to do this at all in order to support OpenServer or UnixWare users.
My pet theory is that MySQL, blinded and distracted by the glitter of gold, have overreached themselves. Fine, if that's the case -- they made a bad decision. Nobody's perfect.
Bullshit. (Score:5, Insightful)
Oh, bullshit. SCO and the OpenServer platform are dieing. This was a quick cash grab and nothing more.
Re:Bullshit? How do you know? (Score:3, Insightful)
Oh, bullshit. SCO and the OpenServer platform are dieing. This was a quick cash grab and nothing more.
--
I'm sorry but I don't think you are not making sense. Even if it was just a quick cash grab, that does not invalidate the post you are responding to. Even if it was a one thing, that doesn't make MySQL AB any less hypocritical.
Besides, how
Re:Not So Free Software (Score:2, Insightful)
This has no bearing on SCO's lawsuit against IBM. Doesn't affect Linux. Just benefits SCO and users and increases sales of mySQL
Re:Not So Free Software (Score:3, Insightful)
They are neither assisting or hindering that country's attack on another country. By selling weapons and ammunition to them they are simply increasing sales, which may help them win the war, but they are not helping.
What?
Re:Not So Free Software (Score:2)
Wha?
This is a database not munitions... You do know the difference, right? Man, I feel stupider for having read your post. Thanks.
Re:Not So Free Software (Score:5, Insightful)
So they got a contract and potential new users.
Re:It's rather simple (Score:2)
Only assuming they are still around after SCO v. IBM, SCO v. Novell, SCO v. Autozone, SCO v. Daimler Crysler Corp (still the issue of timeliness unresolved to my understanding), and Red Hat v. SCO (collectively referred to hereafter as SCO v. Everyone). IMO, this is not a good reason to be opposed to MySQL's partnership agreement. Similarly Ente
And sit back... (Score:2)
Re:And sit back... (Score:2)
Apples and oranges.
Re:And sit back... (Score:2, Informative)
I recently build a webshop. I used MySQL for the main article databases and sqlite for the shopping carts and ordering information. This works very well and very fast, even on our slightly underpowered webserver.
Go PostgreSQL (Score:5, Insightful)
Dual licensing for PostgreSQL... (Score:2)
Re:Go PostgreSQL (Score:2)
Wrong (Score:5, Insightful)
Wrong. The client libraries are licensed such that any non-Free *client application* can only be run on MySQL if it is properly licensed aside from the GPL. I.e. if you only want to run Joomla, then you are OK, but if you run Jamroom, then you need the license.
This is because the client libs were changed from LGPL to GPL sometime ago. Perhaps you missed all the fuss under which PHP threatened to drop support for MySQL?
The whole "dual licencing crap" starts when a company chooses PostgreSQL for its licence only, because it intents to distribute it under another, proprietary licence, and give neither code nor money back to encourage its further free development. Its then another dead end and a code sink for Postgres' development.
You'd think that wouldn't you. And yet every company I can think of that has tried this has either: 1) died or 2) contributed back large parts (though not necessarily all) of their contributions back to the community. In at least one case, a large part of the work for the Win32 port was contributed by a company which provided a forked proprietary version on Windows.
Indeed PostgreSQL is progressing fast enough that I have doubts as to whether a proprietary version with non-trivial extensions could be effectively maintained without giving away all generally applicable aspects of one's code.
The main proprietary versions of PostgreSQL that exist at the moment are by the following companies:
1) Command Prompt. They include a replication technology (the only async replication to work on Windows to my knowledge), but have contributed back many other enhancements to the community.
2) EnterpriseDB. They include an Oracle compatibility layer but employ at least one PostgreSQL developer who works nearly full-time on contributions to the community. They are sponsors or co-sponsors for major enhancements such as two-phase commit, SQL-99 PSM support, etc.
3) Pervasive. They have made a number of major contributions to the community.
4) Fujitsu offers a customized version (at least in Australia) and they have made major contributions to the community as well.
Stupidity (Score:4, Insightful)
Re:Stupidity (Score:2, Insightful)
All others have done it, so get over it. The code is GPL, and there is a company that pays (lots of) developers for everyone to enjoy it and give the world a choice.
Re:Stupidity (Score:5, Interesting)
Interesting Groklaw article [groklaw.net] about some fishy reporting on the issue by Forbes.
Re:Stupidity (Score:3, Insightful)
When you find a bad egg you tend to throw away the entire carton.
Re:Stupidity (Score:2)
And how is this different from... (Score:5, Insightful)
Yahoo handing in a demonstrator....
Google agreeing to censor....
And a massive amount of US companies doing extremely dodgy deals with disreputable regimes, you know like Dick Cheney meeting Saddam Hussein.
So MySql (a relatively poor database before SapDB came in) have agreed to work with SCO to get a bit of cash. Not the most moral decisions but certainly against what those who dealt with Saddam Hussein or the Chinese Goverment its pretty small fry.
Re:And how is this different from... (Score:2, Interesting)
Because SCO will sue us for using MySQL! (Score:5, Insightful)
It's in the SCO press release that the money is to be used to produce a COMMERCIAL version of the database.
That's right looks like they duped the MySQL CEO who didnt read the contract before signing.
http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=172
From the SCO press release:
"The SCO Group, Inc. ("SCO") (Nasdaq: SCOX), a leading provider of UNIX(R) software technology for distributed, embedded and network-based systems, today announced that it has entered into an agreement with MySQL AB to jointly deliver a certified, commercial version of the popular MySQL database"
Re:Because SCO will sue us for using MySQL! (Score:2)
Re:Because SCO will sue us for using MySQL! (Score:2)
Well one reason would be that SCO doesn't have any database software of their own.
What you should really be worried about then is GCC and the Linux kernel, which SCO has contributed to as well.
MySQL is a commercial database already (Score:3, Insightful)
His software's free, and that's good enough (Score:5, Insightful)
Then came the debate as to whether mySQL was pure enough in Licensing. Once again, I didn't care, but thought "how can you criticize a man for giving you something for free?"
Now comes the flap about what else this company does to pay the rent. They still allow free use of mySQL, there's still other alternatives if you don't like his terms, I'm still using more industrial/ACID solutions, and others are still throwing rocks at the mySQL people.
The undisputably weird thing is that the good folks giving away mySQL are taking more abuse from the community than if they'd never given it away at all. How's that for incentive for everyone else???
Scenario. (Score:2)
Later, SCO pulls MySQL AB into court over "violations" and "disputes" over who owns what rights to what code and how that code can be distributed
Then it all comes down to the judge and the contracts. And MySQL AB having to cough up everything for YEARS for the discovery phase of the trial.
So, an error in a contract
Re:Scenario. (Score:3, Insightful)
It doesn't make a bloody difference, because that's
Tainted Code!! (Score:2)
It's in the SCO press release that the money is to be used to produce a COMMERCIAL version of the database.
That's right looks like they duped the MySQL CEO who didnt read the contract before signing.
http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=1720 37 [sco.com]
From the SCO press release:
"The SCO Group, Inc. ("SCO") (Nasdaq: SCOX), a leading provider of UNIX(R) software technology for distributed,
Re:His software's free, and that's good enough (Score:5, Informative)
Which is technically more advanced? PostgreSQL or MySQL? Which is more Free? Which costs less? In every case the answer is PostgreSQL. So I agree with you.
And I suggest you take a better look at PHP, how widely used it is, and the heavyweights that are using it, before calling it 'inferior'.
As someone who regularly programs in Perl, Python, and PHP, I would say that PHP is incredibly advanced for niche applications (preprocessing text/html/xml files) and not advanced at all for anything else. It always feels extremely kludgy in areas like GUI programming or general purpose scripting (both Perl and Python are better fits here), but if you want a program that generates, say a config file, PHP is not a bad fit.
Part of the problem with MySQL though is that it achieved earlier popularity for two reasons:
1) Its main FOSS competitor, PostgreSQL was a bear to use in the 6.5 days and
2) MySQL being a for-profit company was able to leverage centralized marketing.
However, many key features were missing from MySQL early on including any semblence of ACID compliance (still not really there in 4.x in that the consistancy and integrity factors are still not nearly complete). Secondly Date's Central Rule still does not apply to 5.0 in that strict mode can always be turned off (even by a client app), so data integrity constraints can be circumvented by applications. For those of us who understand what an RDBMS is supposed to do both mathematically and business-wise, MySQL is a case of asking for trouble.
At the same time, PostgreSQL has solved nearly every usability issue it had in the 6.5 days. Right now debate seems to center around what the standard says about padding and collating sequences, case folding, and handling space padding of char variables in concatenation. No more wishing you could drop a column from a table (you could not prior to 7.3, I think). As of 8.1 the last major usability issues will be *gone* from PostgreSQL. I refer of course to the requirement to vacuum. autovacuum is now part of the backend process. And xid wraparound is solved too. A warning is automatically generated when xid's start to run out, and the rdbms is now smart enough to shut down rather than let it roll over and cause data loss (this almost never happened, because on nearly any production database, performance would dictate vacuuming long before this would become an issue). At the same time, I am not aware of anything that MySQL can do that PostgreSQL can't do as well. For example:
1) 8.1 will have TPC, and the JDBC driver will support XA
2) Replication/clustering possible using add-ons like Slony and PgPool or PgCluster.
3) If you need access to external servers/table types/etc. there is DBI-Link which is a subset of the SQL/MED standard.
4) Daisy chaining triggers
Re:His software's free, and that's good enough (Score:2)
Currently we use sqlite for this, but it's only OK for small installations (well it's flipping excellent for small installations...) - it doesn't scale properly as you get more active, as you can only have one active write at a time.
Last time I look at firebird it had a lot of issues, although that was about 6 months ago and it might have changed
Re:His software's free, and that's good enough (Score:2)
The PostgreSQL team has pretty much said that they don't want to deal with the reputation of instability that would invariably happen if PostgreSQL was running in the same process space as another program. If installation packaging is your primary concern then this is not a showstopper. It takes some understanding of the internals at the moment
Re:His software's free, and that's good enough (Score:3, Informative)
On the other hand, it serves the needs of a very large market. It was built from the ground up for use in dynamic web sites, it's integration with MySQL is quite good, it is readily extendable, and it's easy to le
Re:His software's free, and that's good enough (Score:2)
When I say advanced or non-advanced, what I mean is how expressive a langauge is in a given environment. PHP is a really great text file preprocessor. This al
Cash up front, thanks. (Score:2)
http://www.theregister.co.uk/2005/10/08/ibm_drops_ sco_countersuit/ [theregister.co.uk]
"While IBM continues to believe that SCO infringed IBM's valid patents, IBM agreed to withdraw its patent counterclaims to simplify and focus the issues in this case and to expedite their resolution. The little discovery that SCO has produced regarding IBM's patent claims makes clear that there is insufficient economic reason to pursue these claims. Since SCO
Re:Cash up front, thanks. (Score:5, Interesting)
http://www.groklaw.net/article.php?story=20051011
you would have found out that SCO paid mySQL.
Money taken from SCO is less money for their FUD machine.
It also gives people stuck on SCO a chance to migrate their stuff slowly to other platforms.
So how is that a bad thing again?
Re:Cash up front, thanks. (Score:2)
I'm assuming he didn't use actual company names in his comment because he figured people on Slashdot had brains. He obviously hasn't been around here long
Re:Cash up front, thanks. (Score:2)
SCO will sue us for using tainted code! (Score:2)
It's in the SCO press release that the money is to be used to produce a COMMERCIAL version of the database.
That's right looks like they duped the MySQL CEO who didnt read the contract before signing.
http://ir.sco.com/ReleaseDetail.cfm?ReleaseID=1720 [sco.com] 37 [sco.com]
From the SCO press release:
"The SCO Group, Inc. ("SCO") (Nasdaq: SCOX), a leading provider of UNIX(R) software technology for di
Re:SCO will sue us for using tainted code! (Score:2)
Its not like you're going to use their commercial version that's been ported to run on OpenSewer and try to run it on Linux or *BSD - for that you'll use the appropriate version - either the GPL or commercial version.
That you'd depend on a SCO press release to be 100% of the story is frightening - according to their press releases, they own unix (at least in some parallel universe).
This is the sort of "kne-jerk reaction" that the folks at MySQL
Market Grab? (Score:2)
There are at least a few people still locked into the OpenServer platform, but sometime in the future, they will have to migrate to Linux after the final nail has been driven into SCO. When they eventually do migrate to Linux, they will have to make some choices as to what database to migrate to as well. Will it be Oracle? Will it be PostgreSQL? We
But (Score:2)
Here is the thing. Even with this new round of partnerships, SCO today has fewer partners than at any time in their recent past. SCO needs these partners more than they need SCO. So I would not be at all surprised if SCO isn't offering some pretty compelling advantages to these would-be partners for providing them with some semblance of credibility.
Yes, but I disagree. (Score:2)
There's no need to transition them with mySQL on SCO to get them to use mySQL on Linux.
If anything, it would be easier to do 1 migration straight to a 100% Linux system than to make 2 migrations (one from old database to mySQL on SCO and the other from mySQL on SCO to mySQL on Linux).
Re:Market Grab? (Score:2)
Re:Market Grab? (Score:2)
I don't see flames on OpenOffice and PostgreSQL running on Windows. Well, PostgreSQL is supported on SCO aswell (I think by EnterpriseDB), so I still don't get why all the bitching goes on MySQL AB.
EnterpriseDB certainly got a bit hard time for it on the PostgreSQL email lists. There were a lot of people who voiced similar concerns. EnterpriseDB said "hey look. This is business as usual and is about helping our customers. Don't read any more into it than that." And that settled it.
MySQL AB got a bit
Supping? (Score:3, Funny)
Okay...
Re:Supping? (Score:2)
In my day we "high-fived Beelzebub".
mysql or postgres (Score:5, Interesting)
Also, mySQL has a totally wrong view of the GPL: see this discussion on debian-legal [debian.org].
-- Get free domain names [ezyrewards.com]
Re:mysql or postgres (Score:2)
Industry support.
Re:mysql or postgres (Score:2)
On the other hand... MySQL is popular because it 'fits' the development approach many open source projects have embraced for a long time - power, flexibility and simplicity, even with its limitations.
I hope MySQL can still be used the same way so everyone can have the best of both worlds. Sometimes you just need a storage engine for your blog or whatever, you know?
Re:mysql or postgres (Score:2)
MySQL hardly has the power or flexibility that PostgreSQL does. Even in 5.0. However....
As for why MySQL is most commonly used. I have been a PostgreSQL user primarily since 6.5 and I switched because I recognized that for my business, the integrity of my data was something that MySQL could not guarantee (thi
Re:mysql or postgres (Score:2)
Sure.
There's also the size of the community around the product. MySQL's is several magnitudes larger than PGSQL's.
It is not the size that matters, but the quantity of high-caliber people who are deeply involved in the project
I.e. I would rather get one right answer than a hundred wrong ones.
Re:mysql or postgres (Score:2)
Why would they do that. They are already quite proprietary in that they used to claim that running any proprietary app that required MySQL also required a commercial license. They have dropped that bit. But still....
Re:mysql or postgres (Score:3, Insightful)
You know OpenServer ships with PostgreSQL, right?
And EnterpriseDB has a similar partnership with SCO for their PostgreSQL derivative, right?
From SCO's perspective this is simple. They have lost partners left and right through the myriad of lawsuits. And they need partners to show some sence of legitimacy. So they are largely paying people for
Re:mysql or postgres (Score:2)
And yeah, it co...
Wait a second. This is completely offtopic. Mod parent down. Whatever. This has been hashed out so many times now.
Okay, how about these? (Score:4, Insightful)
Dolby Labs? They should have revoked Apple's right to use AAC the moment Fairplay came to exist. What a sham!
And Cygwin? We should all boycott Red Hat for that deal with the devil. How dare they!
Slashdot? They refuse to auto-detect Internet Explorer, and then serve up a blank page in those instances. How two-faced of them!
Re:Okay, how about these? (Score:3, Insightful)
Microsoft hasn't filed a multi-billion dollar lawsuit claiming that all of linux is their property.
There's a difference between dealing with the devil and dealing with a competitor. Microsoft isn't that great, but at least still tries to make money by selling product. SCO has shifted their focus as a company to suing people who use linux.
See the difference?
It's like the difference betwe
Re:Okay, how about these? (Score:2)
Gosh (Score:4, Interesting)
Decisions... (Score:3, Interesting)
In other words, I don't think that my enemy's friends are my enemies.
On top of that, has the author considered that our priorities may be completely irrelevant to someone else? It's not like we can all take care of everything... like destroying Sco, and saving the world, and curing cancer, and feeding the poor, etc, etc, etc. At some point we have to start ignoring some of these priorities.
Free as in Speech (Score:3, Insightful)
The key fact some OSS zealots miss is that SCO users only USE products from SCO, they ARE NOT ACTUALLY SCO. Granted, SCO pays MySQL. They're still not who's going to profit from the deal the most. The actual users are going to be. They may be forced to use SCO software. Occam's razor dictates they are because using it voluntarily is, at this time, indefinitely harder to explain.
Please stop trying to keep those poor souls from switching to open source software.
WRONG! (Score:4, Insightful)
It is *not* just a simple porting - it is way beyond that.
MySQL AB proudly displays on their website the news release about scox and mysqlab will be working together ect.
Brutal to ev1, forgiving to MySQL? (Score:2)
That sounds a lot like saying, "we knew it'd piss them off, but we did it anyway!"
Look, I know I'm on the wrong side of this -- Slashdot groupthink is clearly forgiving of this, and I'm just not. But if ev1 had its feet held to the flame, I don't see why MySQL should walk away unscathed. Bottom line: it was a bad decision, and while most of the MySQL users won't care, some do, an
Re:Brutal to ev1, forgiving to MySQL? (Score:2)
MySQL's attitude seems to be a little different from EV1's.
EV1 directly funded The SCO Group and was explicitly supporting SCO's wild "Intellectual Property" claims - even to the extent of, afterwards, paying for advertisements in "Linux Journal" claiming to be "IP Compliant".
MySQL, on the other hand, has not paid SCO anything and is at least claiming that they were more interested in supporting existing and new users of MySQL who happen to be on SCO's platform right now.
Can't say that I'm actually happy
I can see it now. (Score:2, Funny)
SCO Customer: You're not gonna pull that "AutoZone" crap on me, are you?
SCO: No, no, not at all. Hey, aren't you using MySQL for your applications?
SCO Customer: Yes, but it's the GPL'ed version, not the one you licences from them.
SCO: I think that's something for the courts to decide, after the loooong and expensive discovery process.
SCO Customer: WHAT THE...?!?!
MySQL: Hey! Why are you harrassing my end-us
Old joke (Score:2)
Time for a new icon. (Score:2)
Re:Time for a new icon. (Score:2)
Re:Time for a new icon. (Score:2)
Re:Time for a new icon. (Score:2)
They don't want anybody to remember that they were Caldera. That effort is what we should not permit.
Re:Time for a new icon. (Score:2)
Re:Time for a new icon. (Score:2)
That said, The SCO Group is no longer Caldera, even if they chose to use "SCO" in their name in a semideceptive manner.
My guess... (Score:2)
"Sure, I can help you, but I have a special fee structure for organizations/people like you..."
Re:My guess... (Score:2)
Commnunity (Score:3, Insightful)
If you sell beer to the guy who keeps pissing in the well, the townspeople are going to get mad.
SCO Anything (Score:2)
SCO should be made an example of, in fact. Long after SCO blows away in the wind, please avoid buying any products from any company McBride latches onto...like a leach that is.
I do not see how this helps the MySQL community, but I do see how it could help SCO with McBride at the wheel to sell
Licensing issues for MySQL connectors (Score:2)
The situation is different with Java: the MM.MySQL connector (up to 2002) was LGPL licensed, but is now version 3.x of the MySQL GPL licensed connector. This is a good reason to keep a copy of the older connector around!
I *think* that the Python license is usable under either the GPL or the Python license.
This is a real pain - I woul
friggin zealots! (Score:2, Insightful)
Until some of this rhetoric that the F/OSS community has goes away, it won't be taken seriously in many of the "larger" corpe
is there a simple solution? (Score:2)
Re:Not eating with the devil? I believe it. (Score:3, Funny)
Re:Don't try to fool us! (Score:2)
......idiot
Re:No worries... (Score:2)
What, specifically, are you talking about? (Score:2)
Please do specify who you're talking about and provide some quotes to back up this namecalling.
Re:There's freedom and "freedom" (Score:2, Insightful)
Yeah! By the same token, it's a huge shame that the US doesn't support North Korea's ideas about freedom.
Re:Mmhmm (Score:2)
My, that's incredibly logical.
(Not.)