Reply to post: Re: Right.

Re: Right.

"Move fast and break things"

yes, about that... the 'file associations' problem. BROKEN for (certain? only?) Win32 applications. It's getting attention around 'teh intarweb'.

IMPLICATIONS: Micro-shaft is SLOWLY trying to ELIMINATE non-UWP applications!!!

You know they want it. You know that "legacy" Win32 support HAS to be IRRITATING them. They've already SLAMMED THE DOOR on EVERY OS they've made that doesn't have UWP (anything prior to Win-10-nic, even when customers WANT the older ones). They've CRAMMED as much as they can cram and put UWP CRapps in our faces as PANELS in the 'Start Thing'. What MORE can they DO to FORCE everyone to CHANGE to UWP? [other than make it worth our while]

Rumors have 'mongered' that it is Micro-shaft's long-term plan to KILL OFF WIN32. This would mean that ALL future applications are CRapps sold through "The Store", _AND_ it would KILL! OFF! WINE! and _ANY_ sense of compatibility for OLDER APPLICATIONS [that do not spy on you].

So, aside from a conspiracy, WHY would the latest (broken) build of Win-10-nic NOT allow Win32 applications to do FILE ASSOCIATIONS??? That is a basic feature of Windows that has been around since FOREVER...

Linux and FreeBSD (and maybe OS/X) may become the ONLY alternative for small-time application builders [and custom applications built within a corporation for its own use] to be able to install and run an application of your own design, and make it available for OTHERS to do the same [from a binary or source], _WITHOUT_ having to go through some "Store" or "code signing" nonsense to DO it!!!

(I used to like windows because you could do all of that, and wrote some windows applications for company-only use a few of times - but NOW, it's becoming obvious that Micro-shaft does NOT want us to have THAT kind of freedom, unless THEY are "in the loop" - and get their 'piece of the action')