Re: MSDN vs. OSDN
> Ah, oh how relieved I am to hear finally
> the move to industry-standard
> technologies, such as C#, and
> Finally the open source world can
> realize that it can't just go off on
> tangents and develop novel technologies
> and protocols, publish them openly and
> expect everyone to collaborate.
> Finally, we can follow standards
> developed by learned, wise and
> forward-thinking organizations who have
> the finances to spend millions or even
> billions getting things just perfect --
> just right for them to continue leading
> us in specific directions.
While I know the tone of your post was sarcastic, I would
like to point out that standards do cost a lot of money. Simply publishing a document is not enough. You have to negotiate with the various interested parties in a fair forum. You need to work out all of the ambiguities in the document. This is why organizations such as ANSI and IEEE exist. The cost is in the politics. For example, Perl might change any day on the whim of Mr. Wall, but every ANSI Common Lisp implementation must adhere to the standard. It's a bigger responsibility for the latter. While
there are certainly free and open-source versions of standardized languages, that doesn't mean that forming the standard was cheap.