[01:02] we are mozilla, we are teh best example of why never to rewrite. [01:04] heh [01:04] I lay that more at Netsape's feet than Mozilla's [01:05] firefox is quite nice [01:32] firefox IS quite nice. [01:32] but still... never rewrite. [05:35] jrwren: :) :) [07:20] Al Gore works at Mozilla? [10:44] morning [12:20] i definitely did not understand that Al Gore comment. Good morning all. [12:20] Inventing the internet [12:23] oh, lolz [12:59] postgresql 9.6 released! who is excited?!? [13:21] I am [13:22] I sent my old boss the release notes. :) [13:26] ;] [13:27] I did a double take when I saw the announcement said something about scale out. I had to go back, read it again, read the detail. I was saying to myself, "what are they talking about scale out?" Then I found it, and all I could think was. HUH. [13:28] Honestly I've come to realize that all of the interesting SQL DB development is happening in the PostgreSQL camp [13:29] I'm sure the various forks of MySQL are doing something interesting, but PostgreSQL has consistently made me actually give a shit about DBs [13:29] yup [13:29] to the point where I want to adverb my sentences [13:29] mysql is oracle. it is so fragmented between maria, percona, that other one and the oracle mysql that its... sad really. [13:30] Yeah, and Maria is repeating their mistakes [13:32] is drizzle still a thing? [13:34] https://en.wikipedia.org/wiki/Drizzle_(database_server) <- the main site is down [13:34] nope. it just died. There has got to be a story there, but I can't find it. [13:34] Wikipedia (which is never wrong) says the last release was in 2012 [13:35] https://www.quora.com/Why-is-Drizzle-dead [13:35] Good ol' Quora [13:36] did you work with Aker at /.? [13:36] Not ringing a bell [13:37] I think he was way before my tenure [13:37] I started around 2008 [13:38] i found https://web.archive.org/web/20140306052400/http://www.linuxjedi.co.uk/2014/02/is-drizzle-dead.html [13:39] So, not dead, but dormant [13:39] hibernating [14:43] Postgresql is so good, I'm of the opinion that if you are ever tempted to use something else, because of feature X, it would be wiser to implement feature X in postgresql and use that. [15:40] no doubt [15:43] I think our switching cost would be a little high at this point :) [15:44] performance or freedom, pick one [15:44] :/ [15:45] at scale drop the ORM and marry your db (or write a custom business logic/app specific API in front of it [15:45] so at least there's less to rewrite to another db [15:46] yep [15:46] we theoretically support postgres in MediaWiki, but we've never used it in production and, with all of the multi-datacenter (hot-warm) work, I... yeah. mariadb for now :) [15:47] yea [15:47] you end up learning the very deep pitfalls at some point, and at that point you're tied [15:48] greg-g: you'll not, I said tempted to use... as in picking at the start. switching is something else entirely and almost never worth the cost. [15:49] switching a database is either trivial because your app is trivial, or its akin to a rewrite because your app is married to your DB. [15:50] lol... *note* [15:53] jrwren: :) yep yep [15:59] I wish Wordpress supported anything other than MySQL [16:03] i used to care. now I don't, since the mysql/wordpress setup is entirely automatic, it hides the mysql ugliness from me. [16:03] heh [16:03] Yeah [16:04] The only thing that bugs me is I have Oracle codeon my machines [16:04] but then again, I like Virtualbox and have that running [16:04] (the only thing Oracle hasn't completely fucked up) [16:04] ....yet [16:05] hush [16:05] for all we know they're not aware of it yet. [16:05] it still makes me cringe and i run it as minimally as possible. [22:34] jrwren: I see you stated the obvious in that OSX juju bug... wtf are they relying on something that isn't sustainable - don't hardcode os stuff, or at least have a sane fallback