At what point will people learn that this is... just not possible? We can dress it up with fancy terms (DSL, etc) but... any business system will require people to be able to think logically and critically about what they're trying to accomplish, and define it out in great detail. Computer languages are the best way we currently have to translate those details in to a computer, and likely will be for a long time to come.
For what it's worth, I've seen comments within Oracle's own code that refers to their own code as being, and I quote, "a horrible kludge". And the quality of their middleware certainly backed up those comments within their code.
I will say in their developers defense, PL/SQL is such a nasty language that it does make it hard to write sane applications. Which is one of the many reason why I'd never touch Oracle again if I can help it.
That's not what open source is about: http://opensource.org/osd-annotated
Open source just means the source code is available. It doesn't mean the source code has to be distributed with a permissive, 'copyleft', licence. While it's true that when one usually talks about "open source projects" they typically refer Apache, GPL, BSD (et al) licensed code (and culturally that would be a fair description), but when one talks about the code being open source it can also refer to proprietary projects as well (as is the case with some of Microsoft's non-free open source licences).
So my comment makes perfect sense given the parent I was replying to: "I wonder if Oregon has jurisdiction to open-source this stuff. I'd love to see the atrocities.". In this instance, the less permissive open source definition would be valid since:
(1) you wouldn't be able to redistribute the code anyway (the government might force a company to release their source code, but it's even less likely they would want to alter the terms of a copyright agreement (and even less likely for US-based companies given the investment America has in intellectual properties)
(2) you can already read the source code to "see the atrocities" (which was the crux of my point rather than arguing about what classifies as "open source" - but well done for completely missing that point and every other subsequent point)
Lastly, before you turn this into an evangelical licence flamewar; I primarily write and contribute towards GPL projects, so I full endorse and support copyleft licences. In fact I'd go further than that and say that source code that's available for viewing but not for redistribution is more damaging than good; but that's a whole other topic of conversation.
It means what the definition says it means: the source code is available under a relatively liberal license that meets certain requirements:
http://en.wikipedia.org/wiki/Open-source_software
A more accurate version of what you meant might be "I wonder if Oregon has permission to make the source code available for viewing" or something like that.
But even that aside, I never said Oracle's middleware was open source per se, I said it was licensed similarly to open source (though my wording might have been clearer).
Oh and since this is now just an exercise in pedantry, I should point out that you posted a link to Open Source Software while talking about Open Source Licences. Obviously the two are related, but they're not specifically the same thing (though your confusion of the two might explain this discussion)
It's important that people understand that it's not just having the source code, but also a license that allows you to do a series of things with the code. That's a huge, and critical difference, not a minor quibble.
In any event, it'd be fun to see Oracle's crappy code.
Besides, if people want to understand what they can do with the code then they should read the software licence (that's the whole bloody point of it!) rather than just make guesses based on a common perception of a broader software term.
Perhaps some of you would like to come forward and offer your opinions rather than down voting and running like cowards? Or perhaps you're just davidw's alias ;)
One developer experienced in Oracle products called Oracle’s programming “atrocious.” He added that “they broke every single best practice that Oracle themselves have defined. It is one of the worst assessments I have performed * * .” The same developer wrote to Oracle, “You are Oracle people, working on an Oracle hardware platform, with Oracle technology products, on an Oracle solution. * * Oracle should be delivering these environments and products as a solution, like they actually understood the products and owned the solution which has not been the case by a long shot.”
AND
Oracle’s responses to the Vendor Questionnaire also stated that OPA and Siebel, the foundation of the “Oracle Solution,” could be implemented by business analysts, not software developers, and without customization. Oracle explained that “government subject matter experts (not application developers)” could define rules in OPA “in the terms and vocabulary that they are familiar with and/or as defined in relevant statute, regulations and policy documents. * * * There is no scripting or programming needed.”