"Who do we sue" is a bit of simplification. What companies need is around the clock support which they are willing to pay for. Companies pay $Ms to Oracle for support contracts for a reason. My former boss signs a PO every year to Oracle for a few $M. It’s not because Oracle is better than MySQL now days.
Someone to blame is certainly a factor but if you have to use that excuse with your boss(es), you better warm up your CV. As to why not use MySQL instead of Oracle, legacy systems is the reason. If you are already paying for Oracle support, have deployed systems using Oracle, and have people trained up on Oracle, what competitive advantages and risks are there for migrating to Postgres, MySQL, MongoDB,…? Note Oracle is only an example. The same can be applied to other legacy/obsolete technologies like CICS, MQTT,… Regards, Spencer > On Jul 3, 2022, at 18:39, Katherine Mcmillan <[email protected]> wrote: > > Thank you John; I think "reliable" was the wrong adjective chosen by the rep. > I find the "who do we sue?" [when something goes wrong] question problematic > on many levels. I suppose the idea is that they could get in a courtroom > with Bill Gates and/or his legal team, and any issue would get sorted. Sort > of like, if you ever have a problem with your cereal, you could sue Captain > Crunch. > > A figurehead seems to be important, so that people do not ask who they can > sue when something goes wrong. Maybe there needs to be a face under the Red > Hat? If so, I propose it look like Carmen Sandiego :) > > Sincerely, > Katie > >
