Slashdot Mirror
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.'"
Can't we just call them advertisements like the waste of time they truly are?
And just what fraction of Java was community-developed?
As usual, when a company makes this kind of claim, my first thought is 'yeah right', and my second though is that it's mostly FUD to convince people to buy the crap you make.
And, if my limited exposure to Oracle Beehive and a few other things means anything ... Oracle can produce some major-league shit code on their own. That stuff was complete garbage, wasn't even what I'd call a beta, but it was being sold as if it was solid and ready for business.
Lost at C:>. Found at C.
Yes, Oracle Unbreakable Linux is repackaged Red Hat Enterprise Linux.
And the ones he inherited from the Sun acquisition got so pissed off with working for Oracle, they all left as soon as they could.
Blatantly, even.
/etc/oracle-release /etc/redhat-release
[brad@icarus Desktop]$ cat
Oracle Linux Server release 6.4
[brad@icarus Desktop]$ cat
Red Hat Enterprise Linux Server release 6.4 (Santiago)
[brad@icarus Desktop]$ uname -a
Linux icarus 2.6.39-400.209.1.el6uek.x86_64 #1 SMP Tue Sep 10 20:39:39 PDT 2013 x86_64 x86_64 x86_64 GNU/Linux
[brad@icarus Desktop]$
At least CentOS bothered to change the redhat-release file.
Support the EFF and Creative Commons. The war is coming, and they're supporting you...
I came to say what you did. I would add. I have seen brilliant open source projects and crap ones. I have seen brilliant closed source ones and crap ones. That TCO thing is funny. Its like they have never bothered to buy their own flagship product. It is considered one of the highest priced finicky bits of software out there... When you have to hire 2-3 consultants just to figure out how to install and tune it something is wrong.
Man pages are documentation in the same way that -? and --help and .conf file comments are documentation. Assuming you even know the command you want (or apropos can find it when you accidentally use the same name as the developer for something) they typically give you just enough information to know that you should be able to do what you want with the command you've found. These tools are references to remind you what you already know, not teach you what you knew you didn't know already, and certainly not to teach you what you didn't know you didn't know already.
Mind you, most commercial documentation is crap. MS's is better than most everyone, IMX, as their documentation not only includes references but procedures as well. SQL Server's documentation in particular is quite good, although SQL documentation from any vendor is generally stellar compared to any other software product. SQLite, SQL Server, Oracle SQL, MySQL, PostgreSQL, etc. All have stellar documentation.
The road to tyranny has always been paved with claims of necessity.
There have been many third party studies on code quality for large open source and closed source projects. Having worked on both kinds of projects I think you really overestimate the code quality of closed source. A lot of it is simply horrid.
And one of the reasons it *can* be horrid is that it's closed. There's no peer review, and certainly no customer review.
We used to get crap from a vendor that it'd cost huge amounts of money and resources to correct significant, obvious errors in their product. We would tell them "Send us the code. We'll fix it and send it back". And we meant it. For one issue, our admin team sent *them* code, saying "we think this is what you're doing. This other code is what you should be doing." (The problem was fixed, even after they said it'd be too much trouble.) The move to open source was precisely due to frustration with basic, stupid errors that we couldn't fix because we didn't have source.
Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
Oracle is a complex product meant for experts and specialists.