Live data from Hacker News

Oracle makes move to kill open source MySQL

techcrunch.com

81–90 of 97 posts

Re: Oracle makes move to kill open source MySQL

#81
post #6

Earlier quoted context omitted.

Isn't that what MariaDB is for?

An honest question, why support the people who caused this situation in the first place? It really seems like supporting other groups would be more appropriate.

I agree. They shafted us once already.

Re: Oracle makes move to kill open source MySQL

#82

As mentioned in the comments see MariaDB ( http://mariadb.org/ ), an open source fork of MySQL from before the Oracle acquisition. Like Hudson, MySQL will live on.

Yeah, Maria is the fork that people should switch to. Also, it's created by Michael "Monty" Widenius, the original developer of MySQL.

Or PostgreSQL. I've been hearing good things about it lately.

Re: Oracle makes move to kill open source MySQL

#83
post #61

That's the same company that bundles much needed java security updates with the opt-out option of installing a weird browser toolbar and setting the homepage to a crappy service, right? Seriously, I never cared about that company as long as it was just selling expensive (but supposedly feature rich?) software to the enterprise, but it seems the alternatives to Oracle's java and MySQL need some more support, market- a…

MySQL and Java don't affect me much personally, but I think the way they've handled Solaris is a real tragedy for the industry. Larry is the new Bill. I blame Jonathan.

Larry has always wanted to have Bill's place in the world. He's a far worse monopolist than Bill ever was.

Re: Oracle makes move to kill open source MySQL

#84
post #38
post #20

It seems Oracle is on a trend to kill everything open source they've acquired from Sun. Java seems to be the only one left, and it would've happened already if they won the trial with Google, but I'm sure they'll do something equally dumb in the future to kill finally Java, too.

There are other open source projects at Oracle that are still "alive". Like Netbeans.

Why the quotes around "alive"? What has been happening with the Netbeans project?

Re: Oracle makes move to kill open source MySQL

#85

Earlier quoted context omitted.

Not sure what you mean by lack of developer friendliness and what specific tools you find it lacking. Postgres is a great choice for new startups that need an RDBMS and like having schema for their data. There is built-in JSON support in upcoming 9.2 release and most JSON-to-schema mapping should be done in application anyway. Sharding is easy to do at application level; you would lose ability to do certain queries a…

Sorry but PostgreSQL's JSON support is a joke. It is nothing more than a VARCHAR that validates. You can't search or index across fields and the way you actually query the JSON is cumbersome at best. Also all of your arguments are "push to the application layer". Well my point is that with most of the newer databases you don't have to reimplement the wheel.

If you need to store arbitrary JSON fields in the database and index them, then you indeed are better of with some NoSQL database. But I strongly disagree with the statement that all new startups deal with that kind of data organization. Many problems have good structure and can benefit from imposing structure (schema) upfront. In which case any JSON you get will parse in the application, map it to your data organization and store in a clean strict relational format, with all indexable fields extracted to separate columns. I do not store my logs in Postgres, but I do store my billing transactions in Postgres. There are many different types of data with different tradeoffs involved. For most, Postgres is a great choice.

Re: Oracle makes move to kill open source MySQL

#86
post #9

Time to brush up on Postgres or Firebird. Let Oracle shoot off all their feet.

I don't know anything about Firebird. Is it really a good replacement for MySQL?

I wrote an accounts receivable/payable app in Borland Delphi back in 2002. At the time Interbase was the easy choice. At that time, Interbase was transitioning to Firebird. I dropped it in as a replacement and it did its job fine. If you like MySQL, you'll miss auto incrementing Primary Key Columns that MySQL seems to have made so popular. It's not too hard to setup a trigger for sequence types, but it's not built in. (or it wasn't back then) All the tools for management were the Interbase tools. Most of my stuff is either MySQL these days or Postgres when I need good spatial support. I've messed with CouchDB a bit. I just don't see Firebird going anywhere for my needs.

Re: Oracle makes move to kill open source MySQL

#87

Time to brush up on Postgres or Firebird. Let Oracle shoot off all their feet.

Shoot their feet off how? Most people saying "Time to switch from MySQL" (probably) aren't paying for MySQL. From a business perspective, those people are a net loss anyway. Getting them to switch to something else may actually save Oracle a little money.

How many people use a SQL DB without some form of support contract?

To do so is not too smart if your business relies on the DB to function.

Re: Oracle makes move to kill open source MySQL

#88
post #57

Earlier quoted context omitted.

Disclaimer: It's been a while since I tried to use SQLite for anything. I've never really felt that it was actually easier to use than a client/server DBMS. I can imagine that it's good for some kinds of embedded applications, but for normal web applications I don't see any improvement in usability. Juggling files is not any easier than setting up a connection. And there were always annoyances associated with the sim…

1. With the PDO (or any ORM) setting up and "using" SQLite is as easy as any other database. 2. There are several really nice front-ends to SQlite, along with the phpmyadmin like app for SQlite. Like MySQL you'll never have to use the command line (for most operations). 3. SQLite is now included with just about every scripting language (except MS' langs - where it's just a matter of downloading the app and an ODBC dr…

"setting up and "using" SQLite is as easy as any other database"

That's exactly the problem. If it's easier, then maybe I'll use it. If it's just as easy, but does less, I have no reason to bother using it, for two reasons:

1. There is non-zero risk that I will need one of the other features.

2. Even if I don't, why would I want to spend time learning something if it isn't better (at something) than what I already know how to use?

I haven't seen any compelling reason to use SQLite outside of the mobile or embedded space.

"over-kill"

What do you mean by that, and why is it bad?

Re: Oracle makes move to kill open source MySQL

#89
post #61

That's the same company that bundles much needed java security updates with the opt-out option of installing a weird browser toolbar and setting the homepage to a crappy service, right? Seriously, I never cared about that company as long as it was just selling expensive (but supposedly feature rich?) software to the enterprise, but it seems the alternatives to Oracle's java and MySQL need some more support, market- a…

MySQL and Java don't affect me much personally, but I think the way they've handled Solaris is a real tragedy for the industry. Larry is the new Bill. I blame Jonathan.

I personally stopped using MySQL quite a while ago as well. Java, on the other hand, got resurrected for me with Groovy first, then Clojure (and a passing interest in Scala).

Yeah, I know about openjdk. But they don't provide official binaries for all I know (and certainly not for Windows, linking back to the Oracle distribution).

Re: Oracle makes move to kill open source MySQL

#90
post #77

Earlier quoted context omitted.

> ease of clustering and sharding, developer friendliness, JSON support, tool support etc. Which RDBMS do you have in mind ?

Well some are better than others right. Riak/CouchDB are great when it comes to clustering/sharding. MongoDB has the best JSON support and is very friendly for developers. MySQL is proven, has the best tool support and most widely supported. The fact is that just like one programming language doesn't satisfy all use cases. Neither does one database. So maybe PostgreSQL 'supporters' should stop trying to claim it is p…

>RDBMS

>MongoDB

wat

Post reply on HN