4 ms·

I can think of MySQL. While I wouldn't call it dead by any measure it certainly suffered when the spit happened.

by dudus 12y ago

AustinG08 12y ago
Since i'm a newbie and I couldn't find anything with a simple search, could you elaborate on that particular MySQL situation?
- knd775 12y ago
  Original creators left and created MariaDB. MariaDB is now used in place of MySQL in most Linux distros by default. They left after Oracle got control over it by buying Sun (who had previously bought MySQL.)
  - Xorlev 12y ago
    For me it was the closed-source new test cases. That marked a turning point for the direction of MySQL (IMO).
- deleted 12y ago
  [deleted]
- privong 12y ago
  The short version is that MySQL was acquired by Oracle (when Oracle purchased Sun Microsystems). Following concerns about it remaining open source, MySQL was forked by it original creator, and is developed as MariaDB[0]. [0] https://en.wikipedia.org/wiki/MariaDB https://en.wikipedia.org/wiki/MariaDB
- deleted 12y ago
  [deleted]
- peapicker 12y ago
  Personally, I always though that the community over-reacted big time. After all, the core DB engine most people were using for MySQL for years (InnoDB) had been owned by Oracle for years before that. MariaDB has done some decent stuff, tho.
wtbob 12y ago
Yeah, but how much of that was due to forking and how much of that was folks realising that PostgreSQL is much better than MySQL for most metrics of better?
- TallGuyShort 12y ago
  The other thing to consider is that for me to think that forking makes the future of the project questionable, you'd have to show that it's likely that usage(original project) < usage(upstream) + usage(fork). In other words, I'd be interested to know the combined usage of MariaDB and MySQL and see if you could actually predict with confidence that it would significantly lower than original MySQL usage. Not just that one of the forks didn't have as many people.
- bodyfour 12y ago
  Yes, but Postgres had lots of technical advantages of MySQL for years, and still was less popular. For most uses people would decide "MySQL is good enough feature-wise for me. It's so popular it's probably safest ecosystem-wise" It was the MariaDB fork that shook people up. Now suddenly the decision became "should I bet on one of these forks, or should I skip that drama and use Postgres which seems like a nice stable project" The fork is really what changed the game.
- drummer32 12y ago
  I think most of that was because of Oracle buying Sun. The MariaDB for and Postgres's rising popularity are the outcomes of that.
Someone1234 12y ago
By any measure? This web-site indicates no significant decline in MySQL usage: http://db-engines.com/en/ranking_trend http://db-engines.com/en/ranking_trend
gohrt 12y ago
forking didn't hurt MySQL. Going proprietary hurt MySQL.

I can think of MySQL. While I wouldn't call it dead by any measure it certainly suffered when the spit happened.

by dudus 12y ago

I can think of MySQL. While I wouldn't call it dead by any measure it certainly suffered when the spit happened.

Since i'm a newbie and I couldn't find anything with a simple search, could you elaborate on that particular MySQL situation?

knd775 12y ago
Original creators left and created MariaDB. MariaDB is now used in place of MySQL in most Linux distros by default. They left after Oracle got control over it by buying Sun (who had previously bought MySQL.)
- Xorlev 12y ago
  For me it was the closed-source new test cases. That marked a turning point for the direction of MySQL (IMO).
deleted 12y ago
[deleted]
privong 12y ago
The short version is that MySQL was acquired by Oracle (when Oracle purchased Sun Microsystems). Following concerns about it remaining open source, MySQL was forked by it original creator, and is developed as MariaDB[0]. [0] https://en.wikipedia.org/wiki/MariaDB https://en.wikipedia.org/wiki/MariaDB
deleted 12y ago
[deleted]
peapicker 12y ago
Personally, I always though that the community over-reacted big time. After all, the core DB engine most people were using for MySQL for years (InnoDB) had been owned by Oracle for years before that. MariaDB has done some decent stuff, tho.

wtbob 12y ago

Yeah, but how much of that was due to forking and how much of that was folks realising that PostgreSQL is much better than MySQL for most metrics of better?

TallGuyShort 12y ago
The other thing to consider is that for me to think that forking makes the future of the project questionable, you'd have to show that it's likely that usage(original project) < usage(upstream) + usage(fork). In other words, I'd be interested to know the combined usage of MariaDB and MySQL and see if you could actually predict with confidence that it would significantly lower than original MySQL usage. Not just that one of the forks didn't have as many people.
bodyfour 12y ago
Yes, but Postgres had lots of technical advantages of MySQL for years, and still was less popular. For most uses people would decide "MySQL is good enough feature-wise for me. It's so popular it's probably safest ecosystem-wise" It was the MariaDB fork that shook people up. Now suddenly the decision became "should I bet on one of these forks, or should I skip that drama and use Postgres which seems like a nice stable project" The fork is really what changed the game.
drummer32 12y ago
I think most of that was because of Oracle buying Sun. The MariaDB for and Postgres's rising popularity are the outcomes of that.

Someone1234 12y ago

By any measure? This web-site indicates no significant decline in MySQL usage: http://db-engines.com/en/ranking_trend http://db-engines.com/en/ranking_trend

gohrt 12y ago

forking didn't hurt MySQL. Going proprietary hurt MySQL.