Whidbey design goals revealed

Written on the original Movable Type site and recovered from the Internet Archive.

I am thinking alot about how to take advantage of the architecture shift coming with Longhorn. On the dev tools side, there is an interium step from Visual Studio 2003 called Whidbey. Whidbey basically uses existing architectures but is more productive. Next step after Whidbey is Avalon which leverages all the new file systems, databases, forms, etc. The design goals for Whidbey (out early next year) are:

Reduce coding for common tasks > 50 %
Full access to .NET framework
Dramatically reducing programming errors at design time
Simplifying data access
Improving the RAD debugging experience
Delivering high-end features for advanced Visual Basic developers

These would be a big improvement. Microsoft continues to be the best, most integrated development platoform. So a 50% coding reduction is coming soon. What if another 50% comes in 2007? How many developers will be using Linux and it’s tool set when they have to write 5-10x the code?

← the 2003–2012 archive