Bryan Cantrill, co-inventor of DTrace, leaving Sun
dtrace.org
dtrace.org
(though there is historical reasons for that name, not just random swearing)
http://blogs.sun.com/bmc/entry/the_economics_of_software
random quote: "doesn't it strike you as odd that your operating system is essentially free, but your database is still costing you forty grand per CPU?"
A classic, although if I remember correctly the comment makes more sense in the context of the entire thread.
Hence Oracle fits the bill if your company can afford it: It's number one, expensive (which implies good quality), and everyone else uses it. Ergo, no one ever got fired for choosing Oracle, licensing costs be damned.
Also, I'm not aiming to kill Oracle overnight, I'm aiming at slowly chipping away at Oracles dominance. Right now there's a huge market for serving apps that for some reason are locked into Oracle, and are too expensive to re-write.
Heck, they would be negligent not to investigate ways to reduce their costs on behalf of the shareholders.
http://www.enterprisedb.com/products/postgres_plus_as/overvi...
Diversity is more important than Oracle compatibility.
Also, migrating a big Oracle install is not something businesses do. I see lots of big databases that are two or three releases back. And, lets be sincere, Oracle's RDBMS has a lot of clustering/availability features that no free alternative can touch. Its fate will be the one of the mainframe - Oracle (along with Microsoft) will keep losing the lower end at the same time Oracle pushes the higher end forward with new features that don't exist elsewhere.
Oracle discourages technologists from doing this. Bryan has a nice way of phrasing his reasons for leaving. I wish he had left a clue about his future venture too.
Sad but inevitable.
I thought if you're that far up the ladder you have a lot of freedom.
Oracle can't/won't/isn't interested in keeping that culture around, and it is questionable what that culture actually brought about in value at Sun. After all, they weren't very good at making money. Oracle, on the other hand, is very good at making money, and perfectly happy letting the cool people work other places, acquiring their work if they decide they need it.
If there was some sort of news from Oracle, how they weren't interested in a class of products or they weren't interested in technology or anything like that, or maybe all all the senior sun guys were being demoted a notch or seomthing then folks would be screaming bloody murder and we'd all know about it. Oracle wants to continue to make money and Sun was more interested in making their team think they were the best, regardless of what the market showed. That's the difference.
Some of these guys simply might be better off elsewhere, their time might be past, but if they really want to show their greatness then they have an opportunity to do so now with real marketing might. I went through this with a company a few years back, we boot strapped it, got it going, came up with some good ideas and some products but didn't have the money to make them robust and didn't know how to sell; we got bought and maybe a quarter of the team saw that as the ending (nobody made any money at that point) and they put that kind of effort in, the others saw it as time to get real and do the hard work, take things to the next level.. It's just a natural sort of thing when companies get bought.
On the up side, I give the guys that are leaving some credit. They could just hang out and be dead weight, draw probably giant pay checks and not do a whole lot.
One very simple thing we do know about is that many/most?/nearly all??? of Sun's software people have seen their salaries significantly reduced. Even if this didn't hit directly people at Gosling's level it would substantially change a whole lot of things and certainly sends a number of negative messages.
It's not completely grim, the Maxine (JVM in Java) research group seems to be very productive and not losing principles, but they're working on an area that Oracle considers to be critical (JVMs in general and JVMs on top of VMs in particular).
He's one of the most technically intimidating people I've ever met.