Apple steamrolls over 3rd party apps (including implementing features that they rejected another app for including), developers get angry and... this is somehow this is partly Microsoft's fault. Interesting.
Well, the poster I was replying to was kind of saying the opposite. Implying that Microsoft 'spoiled' developers by not implementing those things themselves.
I guess there's a kind of double meaning of "responsible" at work here. I didn't mean to suggest MS was wrongful in their actions - what they did they did for their own purely business oriented reasons and it worked well for them. It just happened that it resulted in a perception that there is an invisible line between an OS and its apps that an OS vendor won't cross and that if you establish a business on one side of the line you can trust that the OS vendor won't squash you. That line was never real, it just happened that Microsoft couldn't cross it for business & regulatory reasons, so they didn't. But now we come to MacOS and iOS and Apple has no qualms about crossing the line but developers still seem to expect them not to. I attribute that partly to this historical perception that came from the MS era.
There's sort of a point there but MS dropped that approach a good many years ago (look at security centre, movie maker and so on) so I'm not sure it's really relevant today.
Even still, anti-virus and movie maker are not default installs (and not even delivered on the install media) which is at least partly attributable to MS still being hesitant to cross that line.
I seem to have movie maker installed and I certainly didn't download it.
Possibly it came down in a Windows Update (I tend to just say "everything") but if that's the case it's surely only the finest of whiskers away from being a default install.
