Microsoft's only choice to move forward is to throw the Win32 baby out with the bathwater. And that brings us to the introduction of Windows 10 S.
Windows 10 S is just like the Windows 10 you use now, but the main difference is it can only run apps that have been whitelisted to run in the Windows Store. That means, by and large, existing Win32-based stuff cannot run in Windows 10 S for security reasons.
To bridge the app gap, Microsoft is allowing certain kinds of desktop apps to be "packaged" for use in the Windows Store through a tooling process known as Desktop Bridge or Project Centennial.
The good news is that with Project Centennial, many Desktop Win32 apps can be re-purposed and packaged to take advantage of Windows 10's improved security. However, there are apps that will inevitably be left behind because they violate the sandboxing rules that are needed to make the technology work in a secure fashion.
"A casualty of those sandboxing rules is Google's Chrome browser. For security reasons, Microsoft is not permitting desktop browsers to be ported to the Store."
(Score: 2) by Scruffy Beard 2 on Thursday May 11 2017, @10:23PM (1 child)
If my audio is acting weird (noise, drop-outs), I fix it by removing pulse audio.
To be fair, that is considered a bug [archlinux.org], but my hardware appears to support mixing though ALSA anyway.
I have found two difficulties with this:
(Score: 1) by Scruffy Beard 2 on Thursday May 11 2017, @10:35PM
- Broken ALSA Drivers [freedesktop.org]
But if you check the bug report, it was closed WONTFIX because the version of Fedora it was reported on reached end of support. Maybe no new comments were added because the driver was fixed in the kernel.