Oracle Attacks Open Source; Says Community-Developed Code Is Inferior
sfcrazy writes "Oracle has a love-hate relationship with open source technologies. In a whitepaper (PDF) for the Deparment of Defense, Oracle claims that TCO (total cost of ownership) goes up with the use of open source. They're essentially trying to build a case for the use of their own products within the government. 'The skill required to successfully and economically blend source code into a commercially viable product is relatively scarce. It should not be done directly at government expense.' Oracle also attacks the community-based development model, calling it more insecure than company developed products. 'Government-sponsored community development approaches to software creation lack the financial incentives of commercial companies to produce low-defect, well-documented code.'"
You said "Government-sponsored community development approaches to software creation lack the financial incentives of commercial companies to produce low-defect, well-documented code."
What you really meant was "Unlike proprietary, hidden commercial code, Government-sponsored back doors in software can't be found in the traditional, open-source, many-eyes, well-documented code.
But that probably doesn't rake in the profits, does it?
Support FSF: Stop thinking with your wallet, and think with your imagination. (cc/non-commercial)
Oracle: "We're buying Sun. Next step is to dismantle (MySQL,) close (Solaris, Java,) dissolve (OpenOffice) and generally disrupt all of Sun's open source properties that we can."
Community: "What? You can't do that!"
Oracle: "Watch us!"
Community: "Well, we'll just fork it."
Oracle: "S---! The forks (MariaDB, Percona, OpenIndiana, LibreOffice) and their pre-existing competitors (Linux, FreeBSD, Dalvik) are getting more popular than our versions! READY THE FUD CANNONS!"
As opposed to Oracle error codes that are documented as "Please contact Oracle support", for shit they know about and have a patch ready for but they have you over the coals and want to extort a couple hundred grand from you.
The question is who you want to pay, and what you want the cost model to be. That is, if it's something with both an FOSS and COTS option.
If you want to pay a vendor a fee, typically based on capacity + professional services, go that way.
If you want to use a FOSS technology, and pay only for professional services, go that way.
Generally I think the FOSS model is much better for customers, because:
1) The customer can scale the business without additional licensing costs.
2) The customer has the flexibility to choose any vendor (or internal staff) to do the work.
So, for example, my last startup grew to 70m users on FOSS software, with hundreds of servers, with only physical server, hosting and bandwidth costs (plus a small dev team, which I would need in any case). If I'd used a licensed OS, database, etc., that cost would have made my business not viable.
Enable 3D printed prosthetics!
This is about Oracle and well they have PostgresSQL beat by a mile
If you need that mile of bookshelves for people to be able to use your product, something has gone horribly wrong.
Ezekiel 23:20