DevJunkie111 said:exoteric said:*snip*
Thank you for all your posts, your comments are insightful.
It is totally overwhelming!
And all of these technologies are evolving rapidly.
Given that writing good UIs is still a great challenge all these different UI technologies and frameworks make it hard for developers to focus on the "real" problem of designing and building good UIs; instead time and effort is spent on learning all these frameworks. These are not just different in terms of ideas like XAML vs HTML for mark up they also differ in strategies for managing state(Client vs. server). If we were going to be investing in HTML5; why could we not have invested in it more, so we would not need XAML? We could have built WPF engine on top of the HTML5 DSL for UIs.
And while we are discussing this, let us think of also of the complexity of many implementations of MVC, MVVM (Too many implementations to list out; corrected based on comments from wkempf).
Is this not getting way too complex?
Of course we should not stop progress in anyway; but perhaps we can do better?
Am I missing something? Please help me understand I really appreciate it.
MVC isn't a library. ASP.NET MVC is, so I'd be picking nits, except you also list MVVM which isn't a library and Microsoft doesn't provide an MVVM framework. These two are patterns, not libraries. And if a pattern is too complex to understand, you've got a much bigger problem than technology advancing on you.
Ignoring this, all of the actual libraries that you find too complex are really just complex because you're new to them. Honestly, they all VASTLY reduce the complexity that exists if you try to do the same things without these libraries. There's a steep learning curve, but once you're over that, you should be more productive. You can't ask for any more than that, I think.