This post originated from an RSS feed registered with .NET Buzz
by Sam Gentile.
Original Post: Refactoring Cut Out of VB.NET Whidbey
Feed Title: Sam Gentile's Blog
Feed URL: http://samgentile.com/blog/Rss.aspx
Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More!
I'm not going to hold back here and I don't care who gets angry. Every single time VB has had the chance to fix it's gross problems (a whole host in VB5 and 6 for instance) and do the right thing, the team does the wrong thing. Finally, VB6 gets replaced with a real language, a first class citizen in VB.NET. Equal playing field, Its The Runtime Stupid and all. Then there were the three differences in VB.NET from C# in CLS Compliance like unisgned ints. Then there was the stupid decision to not turn on Option Strict by default in VB.NET Whidbey. Now, they decided to cut Refactoring (other than Rename Method). But of course, they had tiime to put in the ever useful and foolish My object. Who prioritzed their schedule?? Cutting Refactoring is the single stupidest thing that the team has ever done. Refactoring, as you know from reading this blog, is part and parcel, with Unit Tests, to how real software development is done. By taking this out, the team has deprived the worthwhile VB.NET community of having a true enterprise language (as well as giving their developers the chance to learn an essential skill) and give back its label (I won't repeat what it is) that its had for years. Dumb move.
Previous Topic
