Paul G. Allen wrote:
Name one.
Any system you're running on Windows that you don't expect to have to be
around for a long time.
For example, I know folks who are doing the calculations for movie
special effects using C#. The overhead isn't high enough to make it a
non-starter, it's easier to understand, and once it finishes, you're done.
Any program that will be obsolete faster than C# is won't have a problem
with C# being obsolete.
You calculate the cost of the proprietariness in as part of doing
business. Saying "C# is closed and thus worthless" is like saying
"Adjustable rate mortgages will always fuck you." Nonsense. Sorry if
your business acumen is insufficient to make this sort of judgment.
Given that MS is, to a large extent, working to maintain backward
compatibility in many things, and given that open source projects like
Ruby nevertheless needlessly break backward compatibility with every
minor release, I don't see where having it "open" is that big a win. How
many Java AWT-based applets still run?
It doesn't look like YouTube or Google Video are having a whole lot of
trouble due to using proprietary codecs either.
--
Darren New / San Diego, CA, USA (PST)
His kernel fu is strong.
He studied at the Shao Linux Temple.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
