Microsoft drops C#
Maybe you were surprised about the timeframe change of Visual Studio (codename Whidbey) to 2005. Now its out!
As well informed people reports, Microsoft had some time ago an internal meeting about development languages. “Foxpro, VbScript, C#, VB, Vb.NET, C++, J# - what’s about all for it, what is our strategy?”, asked Bill Gates in this meeting. So they painted a picture what are the languages and their common users.
C++
Hardcore Developer which loves the pain and want to spent 5 times to develop the solution
J#
nice try to enable JAVA Developers to understand the more easier Microsoft world
FoxPro
for all who are near their retirement
Visual Basic 6
for all who are also near retirement and don’t want to make the move to Foxpro
Visual Basic .NET
for the enthusiastic solution orientated Windows developer. Also sometimes seen hacking some things with ASP.NET for the Browser
C#
at the end of the line, what is it good for?
The answer in the Team was there is nothing which not can be done with VB.NET. Also the development process is much faster, easier and cleaner. To drop this language will reduce the project costs about 5% and the total amount of written code more than 12 %. Also Bill has never written one line of code with C#.
Jay Roxe the product manager told in meeting on TechEd Amsterdam, that this is the reason that all Microsoft Speakers must hold their Sessions with VB.NET.
What Microsoft actually is doing, is to build a migration path from C# code to VB.NET. (Codename NOP ) The problem is huge, cause the C# code is mostly complex and could be done with on line in VB.NET. Take a look at functions like isnumeric or cstr.
So there is also a need for training the C# developer to think easier. To help them, one important change in VB.NET is to make the semicolon as comment sign.
In summary this will help a lot of industries. E.g. books had not to be written in 2 editions. Publisher make more money. Conferences save the C# related sessions. VB.NET training classes are better filled. And Microsoft saves a complete product team. Happy End for VB.NET.