Headline: I hope Microsoft continues to pursue MVC (Model-View-Controller) for web applications.
Details: I’ve been quite busy the past year in my software development director role but I really need to work more on some of the websites I maintain. Most of them were deployed prior to 2005 and while still working fine, I don’t find myself very motivated to go back and work on them. First I’d need to convert from ASP.NET 1.1 to 2.0 or above. I’ve usually found that a re-write is less painful!
So, this weekend I finally decided to work on this task and took a look at Microsoft’s Model-View-Controller release. I’m only a few hours into it, but really like what I see. I hope this will also help me with URL issues I face from my old sites. It will be interesting to see how fast I can move with this approach. I don’t have much time these days, but we’ll see.
Likes:
More testable – I’m a big advocate of test driven development. While in truth I use a mix of unit tests and integration tests, I find that Test Driven really improves the overall quality
Simpler URLs – This has always been a problem and while I need to know more, it looks like that will give me a great deal more flexibility without all the overhead of previous solutions
CSS and Performance – The use of CSS (cascading style sheets) should result in better performance than my past sites.
Dislikes
CSS – I know, I just said I like it – or at least it’s performance. But it feels so much like “black magic”. I don’t feel like a disciplined developer when I work with CSS – I feel like someone shooting in the dark as most of the rules are convoluted and lack any real logic.
Flux – I got the latest release (1.0) this weekend and most of the sites and templates out there don’t seem to work. I’m sure this will settle down with time, but right now if feels like the time when Atlas was just changing to be Ajax.
Leave a Reply