
"Unintentionally"
Sure, it's totally unintentional. Oh, you sweet summer child.
An experienced MySQL database engineer has questioned whether Oracle might unintentionally kill off the open source database with its preference for adding features to its proprietary systems. Peter Zaitsev, who worked as a performance engineer at MySQL Inc before the database was bought by Oracle, has published a blog post …
This post has been deleted by its author
Define "worse" ;-)
However you score it these idiots will find a new setting on the idiocy scale."This one goes up fo 11".
Readers may disagree but for my part I reckon VMware got it mostly right for well over a decade and actually wanted to build stuff to make sysadmins happy.
Broadcom are a bunch of motherless funts who strip-mine anything they lay their hands on.
They're not a techno company....they're a predatory accountancy firm. Hoping Oracle dont end up going the same route.
From my occasional engagement with MySQL it did at least look like Oracle took QA more seriously than the previous owners. They spooked enough people for Monty to get a cheer when he launched MariaDB, but I think the main result was a continuing migration of developers and their companies to Postgres. Long may it continue.
Not really, though it does depend on what you mean by performance. Support for binary JSON was added years ago but the format itself isn't that different to the even older hstore. Going binary meant adding index support and optimisations for the planner. MongoDB probably has greater write speed because that's about all it does quickly and all that some people seem to need.
Yes, many anticipated that Oracle’s acquisition would lead to significant changes. While Oracle did improve QA processes, the acquisition spurred concerns about MySQL’s future. This led to Monty Widenius's launch of MariaDB, which was well-received by the community. However, the major outcome has been a continued shift of developers and companies toward PostgreSQL, which is appreciated for its advanced features and reliability. This migration trend seems likely to continue, also for your better understanding, here are some great learning platforms:
1.https://www.w3schools.com/js/
2.https://www.w3schools.com/css/
3.https://iqratechnology.com/academy/
Currently looking at migrating from MariaDB to PostgreSQL. The biggest stumbling block is the number of queries that were implemented on the assumption that all string matching is case insensitive. It means I'm having to audit every part of our data access layer, which is rather extensive.
I switched our systems to postgres in 2008-2009. I'd previously been a big fan of mysql however even then could see postgres looked like a safer bet. The oracle takeover convinced me it was the correct move and all the fallout ever since has just reinforced my belief that I picked the correct tool for the long term.
Use embedded mysql in a mixed hardware/software long running product. So many bugs recently (each release has more serious bugs than the last). Keep getting their sales asking when we'll move to a managed (I.e. cloud solution). Don't seem to understand our systems have to be installed on customer premises... its obvious where the focus is and it is saas.
> Don't seem to understand our systems have to be installed on customer premises...
To paraphrase Upton Sinclair, it is difficult to get a sales droid to understand that you can't move to the cloud when their fat commission depends on their not understanding that.
Sure, but companies have multi-brand strategies for a reason and I think it's reasonable to assume that while some companies might be happy to pay for support for MySQL, they might not be willing to pay for Oracle for the same task. And winding down the open source side of MySQL would have no effect on these companies because they'd still continue to get a database. You can see Oracle's interest in winding down the open source and "community" aspects: a bunch of freeloaders that don't contribute much.