C# standardization moves ahead [news.com]
So, here's my experience with C#. At the beginning of this year I had in mind a software product, to be sold to consumers and small businesses, that would run only on Windows. My strong feeling at that time was that the application should be written in C#. I did not have the opportunity to develop that application. Now that I am thinking about developing it once again, I cannot see C# as a good choice in a programming language. Here's why: The application is a server-type application, ideal to run on a small computer with a small amount of processing power. Writing the app in C# would mean that it can run only on Windows. I see that as a problem. Suppose it made sense to install the server on a low-cost, low-power, network-connected device. Linux would make a fine operating system to run the application. And using Linux, rather than Windows, would probably help to shave $50 off of each device.
How many other developers make a similar choice?
Microsoft, I'm sure, understands the hestitancy of developers to use C#. I'm sure they understand this situation well before they decided to go ahead with .NET. They want developers to think that using C# and .NET does not lock them to Windows, but who is going to believe it? Microsoft has chosen to ask developers this question: choose you this day whom you will serve. If you commit to Microsoft (and .NET), you have to commit totally, or not at all.
Posted by Doug Sauder at October 13, 2002 06:09 PM