Stop using MySQL in 2026, it is not true open source
optimizedbyotto.com
If you care about supporting open source software, and still use MySQL in 2026, you should switch to MariaDB like so many others have already done.\n
  • setsubyou@lemmy.worldEnglish
    2·
    2 hours ago

    I’m not sure I’m on board with this “fewer CVE’s reported means the product is more secure” logic in this article…

  • hummingbird@lemmy.worldEnglish
    8·
    4 hours ago

    With few new features and heavy focus on code base cleanup and feature deprecation, it became obvious to many that Oracle had decided to just keep MySQL barely alive, and put all new relevant features (e.g. vector search) into Heatwave, Oracle’s closed-source and cloud-only service for MySQL customers.

    In case anyone was wondering what is happening

  • sun_is_ra@sh.itjust.worksEnglish
    8·
    4 hours ago

    It used to be LAMP (Linux - Apache - MySQL and PHP) that power the web.

    Linux is the only thing still there.

    Apache is losing ground to Nginx

    MySQL is losing ground to Postgres

    And PHP is ju losing ground to many new frameworks in different languages

    • JasonDJ@lemmy.zipEnglish
      1·
      1 hour ago

      Is there something bad about nginx that I’m missing?

      I prefer it for reverse proxy over apache…I’d just always found it to be much simpler.

      But going forward I’m more likely to use caddy or traefik.

      P could very easily be python now. At least as a surrogate for Django.

  • evol@lemmy.todayEnglish
    1·
    3 hours ago

    Does anyone start greenfield projects with normal mysql anymore? I know Meta internally whole infra relies on some mySQL + object store design pattern but I assume its so heavily modified from upstream atp. My company migrated everything we could to postgres awhile ago