This was a very nice talk. I can’t say that I like all of it (I get the feeling that C# is stuck where it is right now as long as VB.net takes to cover up), but I do like your overall strategy to co-evolve. As I’m more interested in FP: can we hope that you concentrate more on F#? ;) When you don’t want to introduce more stuff into C# because the language got to big please to us all a favor and work on the CLR and make it unterstand type classes :) (of course you only have to supoort this in F# ;) )
It’d be nice to see C# and VB.NET be identical except for minor syntax differences. It’d be nice to see a language conversion assistant to convert from C# to VB and VB to C# from MS. This would greatly help since many .NET shops want to have/support only one language.
3 Comments
Comments
I talk about C# and VB Co-Evol
2009-05-14T14:09:19ZPingBack from http://microsoft-sharepoint.simplynetdev.com/i-talk-about-c-and-vb-co-evolution-on-channel9-and-some-f-%e2%80%a6/
Carsten K.
2009-05-15T00:16:39ZThis was a very nice talk.
I can’t say that I like all of it (I get the feeling that C# is stuck where it is right now as long as VB.net takes to cover up), but I do like your overall strategy to co-evolve.
As I’m more interested in FP: can we hope that you concentrate more on F#? ;)
When you don’t want to introduce more stuff into C# because the language got to big please to us all a favor and work on the CLR and make it unterstand type classes :) (of course you only have to supoort this in F# ;) )
Greg
2009-05-15T10:55:51ZIt’d be nice to see C# and VB.NET be identical except for minor syntax differences.
It’d be nice to see a language conversion assistant to convert from C# to VB and VB to C# from MS. This would greatly help since many .NET shops want to have/support only one language.