3 ms·
Case in point, Drizzle. It had backing from Google, RedHat, Sun, HP, etc. The fork had over 10k commits, and it was supposed to unseat MySQL as the SaaS cloud D
by tmountain 4y ago
Case in point, Drizzle. It had backing from Google, RedHat, Sun, HP, etc. The fork had over 10k commits, and it was supposed to unseat MySQL as the SaaS cloud DB. Then, the project was just canceled because, “nobody had time to work on it”.
Picking boring tech for crucial areas of a business is almost always the best plan.
https://en.m.wikipedia.org/wiki/Drizzle_(database_server) https://en.m.wikipedia.org/wiki/Drizzle_(database_server)
- hodgesrm 4y agoDrizzle failed because it didn't have a use case that made it clearly better than MySQL. It's hard to displace an incumbent DBMS, because they take a long to time to mature internally as well as develop a productive ecosystem.
- tmountain 4y agoSure it did, it provided a default charset that wasn’t latin_swedish_ci. Clearly I am joking, but the selling point was supposed to be that it provided a lean, mean, modernized MySQL replacement. I think the problem was that replacements under the hood don’t necessarily translate to an improved UX.
- hodgesrm 4y agoExactly.