More on Mono
Someone from Slashdot has been reading
The Casimir Effect, if I had to judge from some of their
latest headlines. (And the ensuing debate)
My expertise is somewhat limited to the technological and the scientific. I know that in the past Microsoft has exercised some severely anti competitive practices. These concern mainly Digital Research and OS/2, but Netscape/Mozilla/Firefox/The-browser-that-won't-die is relevant. But some monopolistic firms also gave us the languages that we all know and love today. This is also why Dennis Ritchie can elicit the same response from me as a Grammy winner.
I'm not suggesting that C# isn't a powerful or useful language. Use of C# and related technologies may be the answer to the Java question. My question is this: anyone familiar with the now infamous "Halloween Documents" will recognize that this strategy smacks of a "decommoditization" of protocol. This removal/extension of "commodity protocols" is a strategy to deal with the "Linux problem" out of Microsoft's own internal documents. Can Microsoft, or any company without a strong record of community cooperation and contribution be trusted to provide the means for new software development? This is the same reason that I'm wary of Java, although it remains my language of choice. Sun has an excellent track record of developing software for cooperation. If Microsoft had that kind of a reputation, then of course I'd jump right on the C# bandwagon. As it stands, I'm still on the sidelines with Python and Ruby.
My expertise is somewhat limited to the technological and the scientific. I know that in the past Microsoft has exercised some severely anti competitive practices. These concern mainly Digital Research and OS/2, but Netscape/Mozilla/Firefox/The-browser-that-won't-die is relevant. But some monopolistic firms also gave us the languages that we all know and love today. This is also why Dennis Ritchie can elicit the same response from me as a Grammy winner.
I'm not suggesting that C# isn't a powerful or useful language. Use of C# and related technologies may be the answer to the Java question. My question is this: anyone familiar with the now infamous "Halloween Documents" will recognize that this strategy smacks of a "decommoditization" of protocol. This removal/extension of "commodity protocols" is a strategy to deal with the "Linux problem" out of Microsoft's own internal documents. Can Microsoft, or any company without a strong record of community cooperation and contribution be trusted to provide the means for new software development? This is the same reason that I'm wary of Java, although it remains my language of choice. Sun has an excellent track record of developing software for cooperation. If Microsoft had that kind of a reputation, then of course I'd jump right on the C# bandwagon. As it stands, I'm still on the sidelines with Python and Ruby.
