4 ms·

youtube migrated away from vitess several years ago Mysql product is circling drain under oracles direction anymore. New 8.x “innovation” releases lack any imp

youtube migrated away from vitess several years ago Mysql product is circling drain under oracles direction anymore. New 8.x “innovation” releases lack any important features. even Mariadb is out executing oracle despite being broke! Mysql community is in bad shape too. Official slack channel is avalanche of lazy newbie questions. Official linkedin group is endless spew of “learn sql cheat sheet” Sad. It’s done for. community may still be “enormous” but that is bad thing when its communication channels overrun by sub-bootcamp-level devs

correct_beans 3y ago
Nobody cares. Millions of apps run on mysql despite your objections. Good luck with that one
sgammon 3y ago
I'll believe it when I see it. Millions of applications use MySQL, and Vitess has only matured and grown. They said Java was done like five times. It's in the midst of another massive revival. I think the bet on MySQL is a solid one, and I think reasonable minds should be able to differ about this, so I can't bring myself to be as sure as you seem to be. I can say this: Our app, built on Planetscale and MySQL's protocol, has been fantastic to work with. We run locally against MySQL and H2, and in prod against Planetscale. Everything works really well. Boost, replication, backups, branching, etc etc. We use all of them. Every feature works great, does exactly what it says on the tin. We have never had a single problem. So, in theory, yes, these things are all on a timeline of some kind between life and death, but I find it very hard to believe MySQL or Vitess are near the end of theirs.
- throwusawayus 3y ago
  think of big features added to oracles Mysql in past two years. Thats ten releases: eight most recent 8.0.xx, and 8.1 and 8.2. what are they? are you using any? does it really not worry you at all?
  - sgammon 3y ago
    I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
    - throwusawayus 3y ago
      ok. json columns were put in eight years ago
      - sgammon 3y ago
        Great sounds to me like a fine pace

correct_beans 3y ago

Nobody cares. Millions of apps run on mysql despite your objections. Good luck with that one

sgammon 3y ago

I'll believe it when I see it. Millions of applications use MySQL, and Vitess has only matured and grown. They said Java was done like five times. It's in the midst of another massive revival. I think the bet on MySQL is a solid one, and I think reasonable minds should be able to differ about this, so I can't bring myself to be as sure as you seem to be. I can say this: Our app, built on Planetscale and MySQL's protocol, has been fantastic to work with. We run locally against MySQL and H2, and in prod against Planetscale. Everything works really well. Boost, replication, backups, branching, etc etc. We use all of them. Every feature works great, does exactly what it says on the tin. We have never had a single problem. So, in theory, yes, these things are all on a timeline of some kind between life and death, but I find it very hard to believe MySQL or Vitess are near the end of theirs.

throwusawayus 3y ago
think of big features added to oracles Mysql in past two years. Thats ten releases: eight most recent 8.0.xx, and 8.1 and 8.2. what are they? are you using any? does it really not worry you at all?
- sgammon 3y ago
  I don't really recall because I don't think our database has needed much on top of stock MySQL. Maybe JSON columns? I don't really care. Just being candid as a user; it has not worried me, no.
  - throwusawayus 3y ago
    ok. json columns were put in eight years ago
    - sgammon 3y ago
      Great sounds to me like a fine pace