Earlier quoted context omitted.
Is there an allusion or metaphor implicit here that I'm not getting?
On a tangential note, if you think The Story of O is about an abusive relationship, I'd say you haven't read the book or watched the movie: (i) O willingly enters the relationship (ordeal may be a better word here) and (ii) it's not your usual S&M or Belle de Jour story either, because she also gains power over her lover, e.g. see the last scene in the movie. So, the analogy may be more apt than the crude master-slav…
A Story of O(racle)
21–30 of 64 posts
Re: A Story of O(racle)
#22Earlier quoted context omitted.
^ More hackers need to understand this. When you go pubic with an IPO, the shareholders are in charge. The Board and CEO are elected on behalf of those shareholders. The Board and CEO's function is to maximize shareholder value. If a CEO doesn't consider an extremely generous bid then he is breaking his fiduciary duty to those shareholders, and will be out of a job.
How did Oracle maximize their value by buying Sun? Sun has Solaris, Java, and VirtualBox. All are free. When Oracle took over, everyone that worked for Sun quit. So Oracle paid a lot of money for a bunch of free stuff. Why?
Oracle has claimed they bought Sun for their hardware (e.g. so they could do vertical integration selling like IBM), but that remains to be seen if it is true or not.
Re: A Story of O(racle)
#23Earlier quoted context omitted.
On a tangential note, if you think The Story of O is about an abusive relationship, I'd say you haven't read the book or watched the movie: (i) O willingly enters the relationship (ordeal may be a better word here) and (ii) it's not your usual S&M or Belle de Jour story either, because she also gains power over her lover, e.g. see the last scene in the movie. So, the analogy may be more apt than the crude master-slav…
[deleted]
Re: A Story of O(racle)
#24Much as I dislike this as a developer, this is a smart business strategy for Oracle. Let's face it: at the companies that use Oracle, the developers aren't the one making the call as to what database to use. That's the call of much higher-ups. About the only solution I can suggest is to avoid working for such companies, but I'm be preaching to the choir to say that.
That's true. The higher-ups can say which database to use and hire a bunch of people to set it up. But if the developers ignore them, they have no way of actually determining this. (Which is what's so great about mandates from Higher Up.)
Re: A Story of O(racle)
#25Earlier quoted context omitted.
^ More hackers need to understand this. When you go pubic with an IPO, the shareholders are in charge. The Board and CEO are elected on behalf of those shareholders. The Board and CEO's function is to maximize shareholder value. If a CEO doesn't consider an extremely generous bid then he is breaking his fiduciary duty to those shareholders, and will be out of a job.
How did Oracle maximize their value by buying Sun? Sun has Solaris, Java, and VirtualBox. All are free. When Oracle took over, everyone that worked for Sun quit. So Oracle paid a lot of money for a bunch of free stuff. Why?
Re: A Story of O(racle)
#26Much as I dislike this as a developer, this is a smart business strategy for Oracle. Let's face it: at the companies that use Oracle, the developers aren't the one making the call as to what database to use. That's the call of much higher-ups. About the only solution I can suggest is to avoid working for such companies, but I'm be preaching to the choir to say that.
That's true. The higher-ups can say which database to use and hire a bunch of people to set it up. But if the developers ignore them, they have no way of actually determining this. (Which is what's so great about mandates from Higher Up.)
Re: A Story of O(racle)
#27> The central relationship between Oracle and its customers is a business relationship ... The concerns of developers are just not material at the level of that conversation Sadly, this is why Oracle could buy Sun and not the other way around.
Having an engineering culture and fostering developer mindshare ... hasn't been a bad business choice for companies like Google or Apple or Microsoft (at least in their early days). And last time I checked, all 3 companies mentioned are bigger in market cap then Oracle. What strikes me is ... how the fuck did Jonathan Schwartz allow the selling of Sun to a company who's culture is so different?
In a public company the CEO typically can only recommend to the Board that an acquisition go through. The board can then put it to a shareholder vote.
The real question is "why did he recommend it?" and the answer is because the company had no other options if it wanted to survive.
Re: A Story of O(racle)
#28In the enterprise space the customer is other businesses. Apple does essentially the same thing in the consumer space. The user is more important than the developer.
This is a good thing.
Imagine if airlines treated their relationship with the flier as the most important. Imagine if politicians treated their relationship with constituents as most important.
Re: A Story of O(racle)
#29Much as I dislike this as a developer, this is a smart business strategy for Oracle. Let's face it: at the companies that use Oracle, the developers aren't the one making the call as to what database to use. That's the call of much higher-ups. About the only solution I can suggest is to avoid working for such companies, but I'm be preaching to the choir to say that.
Re: A Story of O(racle)
#30Earlier quoted context omitted.
That's true. The higher-ups can say which database to use and hire a bunch of people to set it up. But if the developers ignore them, they have no way of actually determining this. (Which is what's so great about mandates from Higher Up.)
I worked at a place that had a huge Oracle RAC license. We ran non-mission-critical data collection apps on it, but the app which dispensed drugs in real-time, all over the world, not only ran Postgres, but 90% of the business logic was in DB functions.
Every few days on pgsql.general mailing lists, there is someone asking for a good Postgresql book (the "High Performance MySQL" kind)
Less books = one more tick mark for Oracle.