<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>arihant</author><text>I understand the article walks through the technical aspects. However, having seen a lot of non-savvy users use Internet, I am firmly with WWW. Probably because of association and all major &amp;quot;established&amp;quot; companies using www, people associate it with strength. I have learned it to be important in similar ways that a .com extension is.&lt;p&gt;If the site did not have www, most people assumed it is probably made by kids, who do not have www yet. See, most people do not understand that www is not a domain like .com which you have to buy. So for average joe consumer, it signals strength. For an enterprise customer, it probably does too. So unless your product is for savvy users or zen-like designers, I&amp;#x27;d stick with www.&lt;p&gt;A lot of people think that naked domain is cleaner. It is actually not, since the average mind is conditioned to read www.x.com, and you have &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;x.com&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;x.com&lt;/a&gt;. It&amp;#x27;s cleaner in the sense that a face is cleaner without a nose.</text><parent_chain></parent_chain></comment><story><title>To www or not www</title><url>https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/?utm_content=buffer67bee&amp;utm_medium=social&amp;utm_source=twitter.com&amp;utm_campaign=buffer</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>zimbatm</author><text>After having tried both I&amp;#x27;m very much in the WWW camp. Even though the naked domain looks nicer, it&amp;#x27;s just not worth the hassle.&lt;p&gt;&amp;gt; End users save an extra DNS lookup&lt;p&gt;Most intermediate resolvers will return both the CNAME and A record in one response anyways.&lt;p&gt;Another issue with naked domains is that all the cookies are automatically served on subdomains as well. It&amp;#x27;s just another hassle to worry about when trying to keep the cdn clean or wondering why a session works only in specific cases.</text><parent_chain></parent_chain></comment><story><title>To www or not www</title><url>https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/?utm_content=buffer67bee&amp;utm_medium=social&amp;utm_source=twitter.com&amp;utm_campaign=buffer</url></story>