Just jotting down my notes from the MVP Summit (so I can get on with ALT.NET commentary). I haven’t seen anything revolutionary, but the conversations are always the best thing anyway.
I’ll sum up the entire summit in one word: positive. I thought that the interaction I saw with Microsoft was simply positive across the board. Not perfect mind you, but I’m content.
Here’s what I saw (no names and some specifics omitted for NDA compliance):
- I’m still not thrilled with the Entity Framework and the direction they locked themselves into, but the EF team came prepared to talk about some compromises that might start pushing EF into the usable category for me. I honestly wouldn’t care about the EF, but I’ll probably be back in consulting at some point in the next 5 years at a shop that will only use Microsoft tooling.
- Daniel Simmons gets the “Thickest Skin of the Year” award. Not the Hyperion/Endymion Dan Simmons though.
- I enjoyed the IronRuby and IronPython talks
- The Parallels extensions to .Net are intriguing, but I wish they’d shown more code and fewer slides
- A version of the Open Spaces format was used for some of the MVP Summit. It wasn’t the real deal, but I’d say that it was an improvement. I really appreciate the more interactive formats as opposed to passive watching the slides go by talks.
- Getting asked for some real feedback. Ayende & I got to see behind the curtains on some internal work in the .Net framework that I was pretty happy about.
- I did hear about one thing in the works that has the potential for some community backlash, but they seemed to be interested in reaching out to defuse that backlash.
- The language teams are very serious about ramping up the coding centric features in the Visual Studio IDE. I know a lot of .Net developers think that Visual Studio is the greatest thing since sliced bread, but it’s coding features badly lag Eclipse or IntelliJ from the Java world. It’s nice to see Microsoft starting to work on that gap. I don’t know if they’ll do anything that isn’t already in ReSharper, but I’m looking forward to seeing where they’ll go.
- Listening to no less than Brad Abrams say that they’re taking testability into consideration on all .Net framework design now. Cool.
What I want for Christmas from Redmond
- IronRuby! Even without Rails, I’d love to use RSpec for testing .Net code and writing specs. DSL construction on the CLR, here we come!
- I don’t know if it’ll ever catch on, but F# looks seriously cool
- Transparent lazy loading in the Entity Framework. If they want the Entity Framework to be usable in constructing rich Domain Models, they’re going to have to do this.
- A hook in the Basic Class Library to make the choice of IoC container pluggable. I think it makes a lot of sense for the .Net framework to have some sort of IoC container capability built into the framework, and you know they’re going to do it at some point. Acropolis needs it. Prism needs it. MVC needs it. Heck, even plain jane WPF could use it. Just please make it pluggable when you do that at some point in time.