All of this talk about Asp.Net being a leaky abstraction and having an overly complicated page lifecycle, I have been considering looking at some alternatives to see what all the fuss is about. I am one of those developers who has taken the time to learn a lot about the page lifecycle and am fairly comfortable with it. I don’t think this means that I should get too comfortable. I have to agree that the current model doesn’t really promote good design and separation of concerns like it should. So here is my “alternative to Asp.net” list:
- NHibernate (I know this doesn’t really have to go along with the above)
Language Of The Year
Lastly, there are is the huge learning opportunity that is .Net 3.5 which will become more mainstream with the release of Visual Studio 2008. I have already ready a couple of books on WPF and WCF but I also want to add:
That should keep me busy for a while. The hard part for me is not so much in the learning but in finding ways which I can apply new things to my work while still fitting in with the applications/frameworks we currently have deployed.