Thanks, Microsoft, but I’m still saying no to Windows 10
Not a well-written article, but some good points.  Concerns of mine:<p>* We &#x2F;still&#x2F; don&#x27;t know the contents of the telemetry Microsoft sends back; hubbub seems to have died down. Do we just not care?<p>* Undocumented APIs. Remember when MS had hidden or secret APIs used by, eg, Office, they were forced to document? Those days are back. Consider the APIs for the Acrylic UI, which is implemented in the WinAPI (not .Net) but is only accessible from .Net applications. That&#x27;s tie-in making it attractive for devs to use only MS products for development, too.<p>* Incomplete. There are still settings not in the new Settings app that are found in the Control Panel. Counting from Windows 8 in 2012, that&#x27;s over five years of incomplete settings.<p>* Buggy. Creator&#x27;s Update introduced a bug loading DLLs that made thousands of apps slower to start, and made debugging them close to impossible - all because they changed the module loading code. It looks like they only tested with modules built by Visual Studio, not third party dev tools, and so broke debugging for those developers for... how long?  Six months.  It wasn&#x27;t fixed until the Fall Update.<p>I could go on.  The first two are the most important to me, and I believe should be to other developers too.