Chris Stevens
Been a developer for, well, this is my 8th year. I've used a lot of languages and scripting languages, but now - I work mostly in C-style languages (C# & C++ mainly) and I'm moving from VBScript to PowerShell.
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Been a developer for, well, this is my 8th year. I've used a lot of languages and scripting languages, but now - I work mostly in C-style languages (C# & C++ mainly) and I'm moving from VBScript to PowerShell.
Luca Bolognese: C# and VB.NET Co-Evolution - The Twain Shall Meet
Oct 22, 2009 at 7:44 AMI'm quite interested to see how this will progress. As many other developers may have experienced, I find I have to know both VB and C# to get things done (as well as C, C++, Java, shell scripting, etc.).
Co-evolving the languages, I think, would be quite beneficial - at least to me. This would reduce, if not eliminate, my consistant need to write a library in C# because VB doesn't expose the functionality I need - and, once in a great while, the other way around - then drop the library in my project.
I'm also anxious to learn some F# in the beta version of Visual Studio 2010 I'm testing. I'm intruiged by Luca's comments about F#.
Finally, as the video addresses, it will be interesting to see if this co-evolution will result in a new language eventually.