<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>eikenberry</author><text>&amp;gt; For example, Linux DNS resolution is an arcane mess of upstream components bodged together over decades, about the place where sysvinit was before systemd came along.&lt;p&gt;Systemd has fixed this as well. Using systemd&amp;#x27;s networking stack DNS becomes completely seamless with the rest of the system. It&amp;#x27;s not quite 100% baked for average desktop users, but all the components are there and work great. You&amp;#x27;ll see distros switching to it soon... particularly workstation oriented ones as the wifi stack is soooo much nicer.</text><parent_chain><item><author>derefr</author><text>I’m honestly surprised that Microsoft aren’t working with Linux vendors in an attempt to solve Linux problems &lt;i&gt;by&lt;/i&gt; more deeply integrating Windows-styled solutions into Linux, such that the Linux &lt;i&gt;client&lt;/i&gt; ecosystem becomes more dependent on the Windows &lt;i&gt;infrastructure&lt;/i&gt; ecosystem. That’d be the natural Azure-focused equivalent to “embrace, extend, extinguish.”&lt;p&gt;For example, Linux DNS resolution is an arcane mess of upstream components bodged together over decades, about the place where sysvinit was before systemd came along. I could totally see Microsoft releasing some FOSS Linux über-network-client-daemon that combines DNS, NMBD, and Bonjour resolution together (sort of like Apple’s mDNSResolver) in an attempt to “clean up” that mess—where, just by coincidence, parts of the SMB stack begin to seep directly into the operation of the system. Then a subsumption for Kerberos+libpam+GSSAPI that also supports NTLM; etc. until eventually Linux ends up needing to talk to a real Active Directory Domain Controller to boot. Might be Microsoft’s one, might be a Linux FOSS one—either way, it gives Microsoft an advantage.&lt;p&gt;...but, so far as I can tell, they’re &lt;i&gt;not&lt;/i&gt; doing this. I wonder why not?</text></item></parent_chain></comment><story><title>Microsoft&apos;s “Love” of Linux</title><url>http://pedrocr.pt/text/microsofts-love-of-linux/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>zymhan</author><text>&amp;gt; ...but, so far as I can tell, they’re not doing this. I wonder why not?&lt;p&gt;Because maybe, just maybe, they&amp;#x27;re a tad bit less evil?</text><parent_chain><item><author>derefr</author><text>I’m honestly surprised that Microsoft aren’t working with Linux vendors in an attempt to solve Linux problems &lt;i&gt;by&lt;/i&gt; more deeply integrating Windows-styled solutions into Linux, such that the Linux &lt;i&gt;client&lt;/i&gt; ecosystem becomes more dependent on the Windows &lt;i&gt;infrastructure&lt;/i&gt; ecosystem. That’d be the natural Azure-focused equivalent to “embrace, extend, extinguish.”&lt;p&gt;For example, Linux DNS resolution is an arcane mess of upstream components bodged together over decades, about the place where sysvinit was before systemd came along. I could totally see Microsoft releasing some FOSS Linux über-network-client-daemon that combines DNS, NMBD, and Bonjour resolution together (sort of like Apple’s mDNSResolver) in an attempt to “clean up” that mess—where, just by coincidence, parts of the SMB stack begin to seep directly into the operation of the system. Then a subsumption for Kerberos+libpam+GSSAPI that also supports NTLM; etc. until eventually Linux ends up needing to talk to a real Active Directory Domain Controller to boot. Might be Microsoft’s one, might be a Linux FOSS one—either way, it gives Microsoft an advantage.&lt;p&gt;...but, so far as I can tell, they’re &lt;i&gt;not&lt;/i&gt; doing this. I wonder why not?</text></item></parent_chain></comment><story><title>Microsoft&apos;s “Love” of Linux</title><url>http://pedrocr.pt/text/microsofts-love-of-linux/</url></story>