Thank you !
I would prefer XAML over HTML5 as it provides flexibility, performance and again that is in accordance with my experience. Jerry Nixon from Microsoft has a few good reasons supporting this - blog.jerrynixon.com/2012/05/windows-8-why-i-choose-xaml-metro-over.html
I personally prefer XAML over HTML.. And that's true with most .NET developers. Microsoft internal dev teams spent a long creating and optimising html / winjs. While it cant match xaml and c# performance isn't so bad.
I'd advice to do what you are comfortable with.
Hi, I prefer HTML5/JS the support and community is bigger, hence, the information on web is more complete
The benefit I see with html5 is that you can easily port it with many platforms.
Whilst I cannot say I am a fan of the HTML5/JS programming combo, I do believe it lends a degree to the ease of use for the developer and an aspect of portability to their finished apps; now, with that said, let it be known that the XAML/C# pair are far superior when it comes to programming power and flexibility. They were designed from white paper to functional language to be the brick and mortar of modern Microsoft platform applications, both hosted and local. I do suppose HTML5/JS is suitable for simpler tasks and easier to learn; however XAML/C# is probably the winner of the fight for heavy lifting and overall platform superiority.
Following are the top 10 reasons why I’m in the HTML/CSS/JS space right now.
So here we go...
1. Skill Ready
I and about a kazillion other people in the world have gathered a ton of experience on the HCJ stack. Websites became applications as some point, and they became essential in the enterprise. I would guess that the web stack has drastically more developers than any other stack... but that’s a guess.
7. Query Selection
In XAML, it’s easy enough to give a control an ID and then select it in the code. But how do you select all of every third paragraph, the third element in the grid, or something like that. The answer is imperative code. There’s no part of the object model that you can’t access, but with query selectors in CSS and JS, you can use simple strings like “div#myDiv p:nth-child(3n)” to select every third paragraph in the div with the ID of myDiv.
CSS is amazing. With a collection of style rules, I can style, animate, layout, add images, position things, and a ton more. With declarative CSS code I can make the same HTML view look entirely different. Style rules cascade down to the eventual screen element and allow a developer to set a style globally and then override that style locally given the need.
There’s a JS library called LESS that extends CSS’s capabilities and allows me to set style variable and even do variable math. So I can set the base color of my app to red and then create a number of derived colors (darker or lighter for instance). That way, the change of a single color variable will result in a complete change to my app’s color palette.
If you are going to cut and paste please state your source otherwise it is plagiarism. You do not live in Seattle but Jeremy Foster does: http://codefoster.com/htmloverxaml