You somewhat supported my claims. Every service snoops to some extent.

As for MVVM, you don't need Microsoft to use it. It's just a UI design pattern and in fact is used in several web technologies. Layers? Nothing that you can't do elsewhere. As for .Net, much of it is now Open Source.


>to insinuate has quite a range of meaning, from hinting across implying, suggesting, suppose..
>
>IAC I am not the only one a bit concerned:
>
>http://www.theverge.com/2014/3/21/5533814/google-yahoo-apple-all-share-microsofts-troubling-email-privacy-policy
>http://www.dailymail.co.uk/sciencetech/article-3184827/Is-Microsoft-reading-emails-Windows-10-threaten-privacy-watchdogs-warn.html
>http://www.theguardian.com/technology/2015/jul/31/windows-10-microsoft-faces-criticism-over-privacy-default-settings
>
>http://www.theguardian.com/technology/2015/aug/13/windows-10-sends-identifiable-data-microsoft-despite-privacy-settings
>
>and .Net is a runtime with somewhat favored architecture blocks, which the OP specifically asked about. Telling him about the Java or NodeJS eco systems would be off topic? IAC I do like some aspects of .Net (MVVM, layerd, C# concepts) a lot, why should that be banned as soon as I am not fannish about every change MS dances?
>
>
>
>>
>
>>>>- .NET applications are architected differently.
>
>>>Full ACK
>>>
>>>>A simple conversion will be sub-optimal and could easily have performance issues.
>
>>>No beef with that part, but if enough cost is saved, not even thinking about conversion might be considered premature optimization ;-))