Using GnuTLS avoids the licensing issues that can arise from employing the more common OpenSSL package. For this reason, certain packages such as OpenLDAP are compiled with support for GnuTLS instead of OpenSSL in recent releases of Ubuntu.
In fact, on one of my Ubuntu 13.10 systems I ran ldd on
This is Google's way of maintaining a more cohesive ecosystem, ensuring that any Android device will have a shot at running any Android app (as well as ensuring enough momentum to fund their [huge] investment in the cloud services involved)..
The real answer is they wanted to support the Microsoft ecosystem, not Google's. Good luck with that - you ain't as big as Amazon, Nokia.
Use the best tool for the job. My personal setup is Windows for desktops (I think windows handles multiple monitors better than osx does), OSX for laptops (Apple's hardware is just so much better for portables), and linux for servers. I'm currently typing this on my Macbook Air. Definitely agree with you about dev tools on windows though. If you aren't bought into the
He must have multiple personality disorder. That comment makes so much sense
I think the reality this totally-free-to-say-what-he-wants MS employee is not mentioning is that MS has company-strategic user-hostile motives for Metro
In fact, if you accept Azure as the best reference profile for Windows servers, I'm not even sure there's a way to get a headless Windows server on Azure (try searching "site:windowsazure.com headless" if you don't believe me).
There were a couple of things obviously wrong with it and I asked if they wanted me to fix it up, but they said no, some guy came by every month or two and did stuff to it.
The good news - these mitigations can be applied from outside the apps involved (as of 4.1, no more app recompiling or special-versions needed). The somewhat bad news - there are compatibility issues, and many apps are not compatible with the whole list of protections (see the MS KB article for more info). I also wonder if there are performance impacts from doing so, as opposed to compiling in the mitigations that can be compiled in - but don't quote me on that, I'm not sure
More bad news - it won't work with certain app features, e.g. any code that accesses certain system services at too low a level, so for example DRM-using apps (so many videogames are off the table); and it only intended for desktop apps (so they "do not advise" you use it with system services or server apps).
We tested the 3.0 version, focusing solely on the mitigations that could be imposed from outside the code even in that version - and found that many apps had issues with most, and some with all, of the mitigations (and, a killer for us, it wouldn't work with virtualized apps). Maybe that's improved, not claiming to know.
All in all - it has value if you're deploying legacy apps over which you have no control to a broad array of desktops, and it doesn't break your apps. Frankly, I don't know why the emphasis on IE11
To be clear