XAML vs. HTML5 – A Discussion
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
XAML by far. It's by far my favorite way to develop. I really hope this HTML5="Greatest end all coding option" hype bubble bursts soon. Sure, HTML5 is powerful, but nothing close to XAML. I realize this leaves mobile out of the picture, however I'm considering a desktop application only.
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
-
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
Still, I'd happily go back to GDI-pre-plus if we only could agree on one UI technology.
FILETIME to time_t
| FoldWithUs! | sighist | WhoIncludes - Analyzing C++ include file hierarchy -
Blankenblog[^]:
In Windows 8 development, you have several options for building your applications. XAML is one. HTML5 is one. Platforms, distribution, and everything else being equal, I would pick XAML/C# every time over HTML/CSS/JS, and I’ve been a web developer for 14 years.
Which would you rather use?
Seems to me everyone here likes XAML/C#. I have to 100% agree. I have avoided ASP.NET as much as I can. WIth Silverlight and WPF I get the MVVM pattern, which I absolutely love. Not available with HTML. In my mind JavaScript was one of the worse decisions made on the web. Almost anything would have practibally been better: VB, C++, .... Personally think they should have come up with a language that played nice with XML.
-
Seems to me everyone here likes XAML/C#. I have to 100% agree. I have avoided ASP.NET as much as I can. WIth Silverlight and WPF I get the MVVM pattern, which I absolutely love. Not available with HTML. In my mind JavaScript was one of the worse decisions made on the web. Almost anything would have practibally been better: VB, C++, .... Personally think they should have come up with a language that played nice with XML.
Clifford Nelson wrote:
Not available with HTML.
Ahem: Yes you do[^].
*pre-emptive celebratory nipple tassle jiggle* - Sean Ewington
"Mind bleach! Send me mind bleach!" - Nagy Vilmos
CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier