Dino Esposito posted this blog that reminded me of something that Shannon blogged about here. Dino received a great (albeit short) response that i 100% agree with. there is also another comment that brings up a great point: how to debug declarative code statements? it's a very valid point, and one that i am interested in seeing implementation of. xaml to me seems like nothing more than a hopped up scripting language, and i thought one of the initial points of asp.net was to move web development into a first class OOP design? i do see the benifits of xaml, but i know personally i will continue to use code behind for the meat and potatos of my web applications. xaml does seem quite useful for building mockups/prototypes quickly, but i would be reticent to put any real code into the UI via xaml code. there is a really great article here that breaks down some of the different types of programmers out there, i believe xaml will be more suited for the opportunistic programmer, and i am sure a lot of us started out that way (via VB and all the code you simply CAN'T change as you can't even see it). i am definitely a pragmatic programmer now and am comfortable with that. what kind of programmer are you? how do you see yourself using xaml practically?



No comments yet