Why industrial standards?
Why do we need open industrial standards?#
1. Everything needs to be able to communicate with everything else – code has to be frozen therefore. A standard is only a standard when it freezes.
2. No black boxes – advantage of a black box is it does the job it was built to do. The problem is it does nothing else. Also black boxes cannot be modified by others. Plumbing problem – imagine building a kitchen where pipes don't fit with other pipes. Whereas everything is handmade with activist geeks – going back to the medieval age rather than industrialization. We are seeking the industrialising of programming.
3. “Documentation” of the black box doesn't fix problems, because actually no one documents, so this is a fantasy solution. Having tools which can allow a community to build around them is a solution.
4. Why java? – it was an open source solution built for industry, and it uses open industrial standards. The whole of java is about standards – it is an industrial language.
5. Don't use instead the fashionable solution. There are no standards for python / ruby / groovy..... Java has been through and won a war to get to be a standard. We don't want to take a newer language and try to make it standard.
.6. We need the standard, rather than the perfect. (eg Transmission and the “perfect” rss which no one else could use). Analogy: Dublin Core for metadata tags announced itself as the victor rather than going through the war to become a standard.
7. Industrial standards have gained from compromises and stood the test of time. (Dave Winer became a hate figure over the standardisation of rss).
8. So don't create new standards (they by definition aren't standards).
9. Everyone wants to be creative in making the machine – you have to standardise the machine to let people be creative.