I think I've finally figured out MS's C# strategy. C# is now an ECMA/ISO
standard. However, that's only true of the current incarnation. The next
version, Whidbey, is not.
http://msdn.microsoft.com/vcsharp/de...rp_preview.asp
So the game is that 3rd parties providing C# implementations will always lag
behind Microsoft. I doubt that C# standardization will ever stop, but there
will always be this time delay between Microsoft going public with their
next C#, the ECMA and ISO standardizing what was done, and 3rd parties
providing compliant implementations. Ergo, C# is open, but MS becomes the
de facto source for the most real world useful solution. You *could* write
to the standardized subsets, but in industrial practice, plenty of shops
will creep into the next incarnation.
MS will keep adding features to C# indefinitely. If they ever stopped
adding, then they'd no longer be able to lead people around by the nose.
Ergo, I predict C# will evolve into a feature laden, baroque language.
Or is there early release information for 3rd party compiler developers and
the ECMA / ISO? That would somewhat change my viewpoint as it would cut
down the latency advantage. Leading the pack and creeping featuritis
wouldn't change though. It's not like there's a standards body controlling
*the next rev.* It's standardization in hindsight, not foresight.
Cheers, www.indiegamedesign.com
Brandon Van Every Seattle, WA
"The pioneer is the one with the arrows in his back."
- anonymous entrepreneur
