I know, as a XAML developer, you are probably confident that you own the better way for writing stunning interfaces, with a productive timing, a consistent toolset and a powerful language like C# that is a sweet juice. I'm also pretty sure that HTML people is completely confortable on its side and do not feel the need of moving to another language. Unfortunately, landing on the real world, these strong reasons are not so strong for all the people, and often you are forced to rely on something you'd not use under normal conditions, as an example because your customer has some constraints that prevent you from use your consolidated XAML or HTML5 knowledge but wants the other.
It's the main reason that convinced me to improve my knowledge in the HTML way to the Windows Store apps - also if I'm totally productive with the XAML side - together with personal will of being aware of all the technologies in my scope. During this exploration I've always kept my XAML knowledge as a guide to understand how the HTML apps works and I found that, under the hoods, the things are not so different and I think that someone may go on the same path backward from HTML to XAML, reading this ebook.
It's the main reason that convinced me to improve my knowledge in the HTML way to the Windows Store apps - also if I'm totally productive with the XAML side - together with personal will of being aware of all the technologies in my scope. During this exploration I've always kept my XAML knowledge as a guide to understand how the HTML apps works and I found that, under the hoods, the things are not so different and I think that someone may go on the same path backward from HTML to XAML, reading this ebook.
