Microsoft Edge is focused on web standard, interoperable technologies. The Universal Windows Platform is the successor for Silverlight (XAML/C#) and can easily be deployed without the need for a browser.

Universal Windows Platform should run in browser. I hope MS is running some analytics and realize nobody is using Universal Windows Platform or Metro applications from windows store. Neither companies or developers are investing in windows store applications. Windows mobile is such a failure also that MS have to invent a way to run android applications in windows 10 mobile because nobody is developing apps for windows mobile.

I hope MS realizes there is lot of potential in creating LOBs applications in browsers using XAML/C# and that developers and companies WANT to invest on that as this an other threads show.

Do you guys even understand your own technology? UWP is NOT the successor to Silverlight! Silverlight was meant and intended to be a C-R-O-S-S P-L-A-T-F-O-R-M runtime for .NET applications, which just so happened to be hosted in a browser. You cannot simply say that UWP is the successor when it cannot even run on a Mac!! Furthermore, this vote is asking you to help R-E-I-N-V-E-N-T a web-standard, interoperable technology that supports MSFT's .NET ecosystem. Otherwise, the cataclysmic developer divide that YOU are helping to foster and perpetuate only widens -- which ultimately hurts YOU!!!

Seriously. Which intern posted this thoughtless and obviously ignorant refusal? This clearly shows the Edge team is a pack of #unnovative, paycheck-dancing followers and simply do not have the heart for innovation.

So which is it? UWP or HTML5? Again, do you guys even understand your own company and technologies? You just don't get it it. You should be building a technology that UNIFIES the schism in the .NET developer ecosystem, not separates if further. By providing two paths to build applications, you are causing confusion and wasting your resources! This ends up not only being expensive for the developers (and companies) who loyally follow you, but for the shareholders that invest in your cause -- this WILL hurt your bottom line and the golden handcuffs that bind you to them, team. Very sad precedent.

Btw, does anyone actually read the vote? It's to R-E-I-N-V-E-N-T way of providing the functionality that Silverlight provided with the new Edge browser (and other Microsoft technologies).

@Brandon, if you have used non-web technologies to create an application/system, and then tried to use web technologies, you will most undoubtedly know the difference. The ask here is to provide an IDE experience where C#/Xaml is used to create the applications, and then from there the application artifacts are created so that they can be run in a browser (and viewed/experienced anywhere). Technically, this is not an Edge technology specifically (per se), but the Edge team should most certainly be aware of it and assisting where needed -- as well as accounting for the .NET framework as a first-class citizen of its development experience.

As for coupling markup to layout, there are Styles in Xaml that are quite nice and robust, and work much better than CSS. Have you tried them? Also, have you seen the new Xaml layout in Windows 10? Very responsive-friendly. It should be, as Windows 10 is meant to be viewed on many different devices.

I would also like to challenge you on my "silly" argument about div's. It's not an "element" ... it's a "div" ... conceptually it's an "element" but you wouldn't know it by looking at it. The point here is that it is not tied to any one thing, which is just a sliver of confusion experienced when dealing with a paradigm that is not congruent/consistent like Native/Xaml/.NET/Java.

@Michael Desmond -
On the #WinDev slack, XAML developers are always complaining about things that are trivial to do in modern HTML/CSS. Your complaint about "div" is kind of silly. It's basically the "element" tag. Layout is controlled via CSS, which is actually a huge advantage over XAML. Doing a responsive layout in XAML is a real PITA, or completely impossible. In HTML/CSS, you can have a <div class="message-list"> where .message-list is a grid at >768px width, and a vertical listview at 768 or less. The lack of proper stylesheet support in XAML, and the tight coupling of markup to layout, is a huge weakness. It's weird to see someone tout that as an advantage when it clearly isn't.