The Rise and Fall of CORBA (2006)
&gt;To create quality software, the ability to say “no” is usually far more important than the ability to say “yes.” Open source embodies this in something that can be called “benevolent dictatorship”: Even though many people contribute to the overall effort, a single expert (or a small cabal of experts) ultimately rejects or accepts each proposed change. This preserves the original architectural vision and stops the proverbial too many cooks from spoiling the broth.<p>“Focusing is about saying no.” -Steve Jobs, WWDC ‘97 -- As sad as it was, Steve Jobs was right to “put a bullet in OpenDoc’s head”.<p><a href="https:&#x2F;&#x2F;donhopkins.medium.com&#x2F;focusing-is-about-saying-no-steve-jobs-wwdc-97-ff0174c171d0" rel="nofollow noreferrer">https:&#x2F;&#x2F;donhopkins.medium.com&#x2F;focusing-is-about-saying-no-st...</a><p>And also:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16227249">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=16227249</a><p>DonHopkins on Jan 24, 2018 | parent | context | favorite | on: Ted Nelson on What Modern Programmers Can Learn fr...<p>In the ideal world we would all be using s-expressions and Lisp, but now XML and JSON fill the need of language-independent data formats.<p>&gt;Not trying to defend XSLT (which I find to be a mixed bag), but you&#x27;re aware that it&#x27;s precursor was DSSSL (Scheme), with pretty much a one-to-one correspondence of language constructs and symbol names, aren&#x27;t you?<p>The mighty programmer James Clark wrote the de-facto reference SGML parser and DSSSL implementation, was technical lead of the XML working group, and also helped design and implement XSLT and XPath (not to mention expat, Trex &#x2F; RELAX NG, etc)! It was totally flexible and incredibly powerful, but massively complicated, and you had to know scheme, which blew a lot of people&#x27;s minds. But the major factor that killed SGML and DSSSL was the emergence of HTML, XML and XSLT, which were orders of magnitude simpler.<p>James Clark: <a href="http:&#x2F;&#x2F;www.jclark.com&#x2F;" rel="nofollow noreferrer">http:&#x2F;&#x2F;www.jclark.com&#x2F;</a><p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;James_Clark_(programmer)" rel="nofollow noreferrer">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;James_Clark_(programmer)</a><p>There&#x27;s a wonderful DDJ interview with James Clark called &quot;A Triumph of Simplicity: James Clark on Markup Languages and XML&quot; where he explains how a standard has failed if everyone just uses the reference implementation, because the point of a standard is to be crisp and simple enough that many different implementations can interoperate perfectly.<p>A Triumph of Simplicity: James Clark on Markup Languages and XML:<p><a href="http:&#x2F;&#x2F;www.drdobbs.com&#x2F;a-triumph-of-simplicity-james-clark-on-m&#x2F;184404686" rel="nofollow noreferrer">http:&#x2F;&#x2F;www.drdobbs.com&#x2F;a-triumph-of-simplicity-james-clark-o...</a><p>I think it&#x27;s safe to say that SGML and DSSSL fell short of that sought-after simplicity, and XML and XSLT were the answer to that.<p>&quot;The standard has to be sufficiently simple that it makes sense to have multiple implementations.&quot; -James Clark<p>My (completely imaginary) impression of the XSLT committee is that there must have been representatives of several different programming languages (Lisp, Prolog, C++, RPG, Brainfuck, etc) sitting around the conference table facing off with each other, and each managed to get a caricature of their language&#x27;s cliche cool programming technique hammered into XSLT, but without the other context and support it needed to actually be useful. So nobody was happy!<p>Then Microsoft came out with MSXML, with an XSL processor that let you include &lt;script&gt; tags in your XSLT documents to do all kinds of magic stuff by dynamically accessing the DOM and performing arbitrary computation (in VBScript, JavaScript, C#, or any IScriptingEngine compatible language). Once you hit a wall with XSLT you could drop down to JavaScript and actually get some work done. But after you got used to manipulating the DOM in JavaScript with XPath, you being to wonder what you ever needed XSLT for in the first place, and why you don&#x27;t just write a nice flexible XML transformation library in JavaScript, and forget about XSLT.<p>XSLT Stylesheet Scripting Using &lt;msxsl:script&gt;:<p><a href="https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;dotnet&#x2F;standard&#x2F;data&#x2F;xml&#x2F;xslt-stylesheet-scripting-using-msxsl-script" rel="nofollow noreferrer">https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;dotnet&#x2F;standard&#x2F;data&#x2F;xml&#x2F;xs...</a><p>Excerpts from the DDJ interview (it&#x27;s fascinating -- read the whole thing!):<p>&gt;DDJ: You&#x27;re well known for writing very good reference implementations for SGML and XML Standards. How important is it for these reference implementations to be good implementations as opposed to just something that works?<p>&gt;JC: Having a reference implementation that&#x27;s too good can actually be a negative in some ways.<p>&gt;DDJ: Why is that?<p>&gt;JC: Well, because it discourages other people from implementing it. If you&#x27;ve got a standard, and you have only one real implementation, then you might as well not have bothered having a standard. You could have just defined the language by its implementation. The point of standards is that you can have multiple implementations, and they can all interoperate.<p>&gt;You want to make the standard sufficiently easy to implement so that it&#x27;s not so much work to do an implementation that people are discouraged by the presence of a good reference implementation from doing their own implementation.<p>&gt;DDJ: Is that necessarily a bad thing? If you have a single implementation that&#x27;s good enough so that other people don&#x27;t feel like they have to write another implementation, don&#x27;t you achieve what you want with a standard in that all implementations — in this case, there&#x27;s only one of them — work the same?<p>&gt;JC: For any standard that&#x27;s really useful, there are different kinds of usage scenarios and different classes of users, and you can&#x27;t have one implementation that fits all. Take SGML, for example. Sometimes you want a really heavy-weight implementation that does validation and provides lots of information about a document. Sometimes you&#x27;d like a much lighter weight implementation that just runs as fast as possible, doesn&#x27;t validate, and doesn&#x27;t provide much information about a document apart from elements and attributes and data. But because it&#x27;s so much work to write an SGML parser, you end up having one SGML parser that supports everything needed for a huge variety of applications, which makes it a lot more complicated. It would be much nicer if you had one SGML parser that is perfect for this application, and another SGML parser that is perfect for this other application. To make that possible, the standard has to be sufficiently simple that it makes sense to have multiple implementations.<p>&gt;DDJ: Is there any markup software out there that you like to use and that you haven&#x27;t written yourself?<p>&gt;JC: The software I probably use most often that I haven&#x27;t written myself is Microsoft&#x27;s XML parser and XSLT implementation. Their current version does a pretty credible job of doing both XML and XSLT. It&#x27;s remarkable, really. If you said, back when I was doing SGML and DSSSL, that one day, you&#x27;d find as a standard part of Windows this DLL that did pretty much the same thing as SGML and DSSSL, I&#x27;d think you were dreaming. That&#x27;s one thing I feel very happy about, that this formerly niche thing is now available to everybody.