8 ms·
There are a lot of issues with this article - Windows S is no more a 'new' OS than an environment running AppLocker is a new OS. The $49 'upgrade' from WinS to
by oceanswave 9y ago
There are a lot of issues with this article - Windows S is no more a 'new' OS than an environment running AppLocker is a new OS. The $49 'upgrade' from WinS to a 'full' Windows 10 is simply removing the restriction, it's the same OS through and through
UWP doesn't explicitly require XAML as part of the stack directx and win2d provide more direct access to graphics hardware
Edge is not a Native UWP application - whatever that means - it's possible to take existing applications and package them to run as a UWP applications, even ones that use COM and Win32. The rendering engine that Edge uses is actually part of the UWP stack - any HTML+JS UWP app uses EdgeHTML as the layout engine. The JavaScript engine, chakra, is a cross platform open source c/c++ library
What MS is doing with WinS is attempting to promote a walled garden and changing windows into a closed platform.
WinS is the first consumer facing foray to this approach. Somehow announcing this in the same breath as education makes it ok.
It might be a noble effort to try to sandbox windows apps, however there are some major detractors: 1) The MS store is a mess, it combines the worst parts of the android App Store and the walled approach of the iOS App Store. But nobody seems to be committed into cleaning it up. 2) not having a compelling mobile story makes existing devs look elsewhere - even Microsoft itself. 3) eliminating compatibility for a broad swath of applications is orthogonal to the approach that Windows has had for decades.
Windows S is the freemium strategy applied to Operating Systems
- UK-AL 9y agoWhat do you mean edge is not UWP native? Are you saying it uses Win32?
- allenz 9y agoEdge is built into Windows at a lower level than UWP. It is UWP-like in the sense that it has the modern app UX on all Microsoft products, it uses the new APPX package format, it favors the new WinRT API, it uses the new AppContainer sandbox, etc. But Edge can also do things that UWP apps can't do, such as being bloody uninstallable, running executable files, and creating special AppContainers[1]. I should also mention that UWP and Win32 aren't mutually exclusive; UWP is an overarching framework that supports WinRT and a subset of Win32 (now called the Windows API).[2] Edge uses some of the Win32 API as well. [1] https://blogs.windows.com/msedgedev/2017/03/23/strengthening-microsoft-edge-sandbox/ https://blogs.windows.com/msedgedev/2017/03/23/strengthening... [2] https://msdn.microsoft.com/en-us/library/windows/apps/br205757.aspx https://msdn.microsoft.com/en-us/library/windows/apps/br2057...
- jetti 9y ago>Edge is not a Native UWP application - whatever that means My assumption is that it is compiled with .NET Native[0]. That would explain why it is only available on Windows 10, as only Windows 10 supports .NET Native. [0] https://msdn.microsoft.com/en-us/library/dn584397%28v=vs.110%29.aspx?f=255&MSPPError=-2147217396 https://msdn.microsoft.com/en-us/library/dn584397%28v=vs.110...
- oceanswave 9y agoIt's not, it's written in C++
- digi_owl 9y ago> it's possible to take existing applications and package them to run as a UWP applications, even ones that use COM and Win32. I was under the impression that this was strictly verboten. Because if this was the case, then why did Mozilla drop its efforts to UWP-ify Firefox?
- oceanswave 9y agohttps://msdn.microsoft.com/en-us/library/windows/apps/mt592904.aspx https://msdn.microsoft.com/en-us/library/windows/apps/mt5929...
- digi_owl 9y agoSo in other words one have to wrap the Win32 code like it was UWP and attempt to push it through the store. Yeah, that's going to become real popular...