Slashdot Mirror
Is MySQL Planning a Change of Tune?
Iggy writes "After reading the article on 'The MySQL License Question' by Timothy R. Butler at Open for Business I just have to wonder, is this company's wording on the MySQL site indicating the company is backing away from Free Software, specifically, the GPL? Great reading and certainly thought provoking."
Like a lot of us are. Their interpretation is a bit off and I'm sure they'll correct it.
Consistency in a database is important too, whatever they choose I'll stick with Postgresql.
If they wanted you to own it, they would have named it that way.
TheirSQL
*snicker snicker*
The classic "farewell and fork you!"
Commercial Software
a few guys then
a few products then
early success then
money! then
more guys then
a few more products then
more money!
then more products (some good some bad) then
more money! then
more guys then..
OSS:
a few guys then
a few products then
early success then
fame and glory for a few guys then
more guys then
a few more products then
some fame for more guys then
maybe some people will join here and there then
a few bug fixes and patches then
not really any fame for the new guys then
people just stop caring because..
it suddenly dawns the german dork who spent 3 months in his basement writing a slighly faster screen refresh algorithm for some OSS spreadsheet program that has 1% market and that is pretty much only due to some for-profit entity working to the letter but not the spirit of the GPL that a) deep down, nobody gives a damn about where their spreadsheet screen refresh algoritm comes from and b) that there is an outside, and that even chasing girls unsuccessfully is better than working for redhat/ibm/whatever without getting paid.
How about mixing in some evidence or facts in your rant?
How did this pile of shit get marked insightful too?
Interestingly, this gave MySQL a niche in the small/medium website market. People who couldn't justify the complexity of earlier builds of Postgres jumped on MySQL because - although it makes the hard things impossible - it makes the most common tasks in a dynamic environment manageable for even the most clueless n00b.
/. while still feeling superior because their code is "fast" and "that's all that matters". I imagine that these folks would attempt to use MySQL to write Banking code. I just hope I can find out what projects these people work on so I can avoid those products like the plague.
Actually... it's more like folks jump on MySQL because they don't have any idea what a database does or is used for and they don't really understand their problem to begin with. They think databases are just somewhere to shove data and pull it out later. Typically, these people will poo-poo things like transactional security, referential integrity, and the like, claiming that no one needs them, when in fact, they don't understand what they are or what they're for. In the end, these people shovel out code that is potentially far worse than anything they flame on
These are the types of things that not having formal training in CS and the like get you. Some self-taught basement dweller who obviously knows all there is to know about computers because they are able to download and install Linux declares that transactions, referential integrity, stored procedures, and the like are worthless. It's hard to use something that you don't understand. Not understanding what the features of a real RDBMS gives you causes you not to use them. Ignorance isn't always bliss.
...am I on crack?
No idea.
Got modpoints?
Writers imply. Readers infer.