<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>Wintamute</author><text>The &amp;quot;holy grail&amp;quot; architecture whereby the first request sends a fully formed HTML response which is then immediately hydrated with a JS frontend app that takes over routing and data gathering is now pretty technically feasible. It&amp;#x27;s the best of all worlds ... fast static content for the first load, and then fast frontend routing thereafter. If you ward your clients away from this path you&amp;#x27;re doing them a disservice. With this stack JS web apps no longer need to be app-like, they&amp;#x27;re well suited to content-heavy sites too. They even work with JS turned off :)</text><parent_chain><item><author>TimJYoung</author><text>This is what I tell potential customers that are evaluating our product that creates single-page web applications where the JS dynamically creates all content: if you want search engines to crawl the content, then you&amp;#x27;re not using the right product.  It&amp;#x27;s a surprisingly easy decision when viewed in those terms.  Most SAAS products that likely would be implemented as SPAs do not care about public search engine access, and are only used by B2B customers where you can dictate a certain minimum standard in terms of browser versions (IE).&lt;p&gt;Everything else should be a traditional static web site with &amp;quot;decorative&amp;quot; JS, or &amp;quot;progressive enhancement&amp;quot;.</text></item></parent_chain></comment><story><title>JavaScript web apps considered valuable</title><url>http://molily.de/javascript-web-apps/</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>onion2k</author><text>Google can and does crawl Javascript driven web apps. Last year they even deprecated the AJAX crawling scheme that they used to recommend on the basis that they can now crawl web apps: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;googlewebmastercentral.blogspot.co.uk&amp;#x2F;2015&amp;#x2F;10&amp;#x2F;deprecating-our-ajax-crawling-scheme.html&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;googlewebmastercentral.blogspot.co.uk&amp;#x2F;2015&amp;#x2F;10&amp;#x2F;deprec...&lt;/a&gt;</text><parent_chain><item><author>TimJYoung</author><text>This is what I tell potential customers that are evaluating our product that creates single-page web applications where the JS dynamically creates all content: if you want search engines to crawl the content, then you&amp;#x27;re not using the right product.  It&amp;#x27;s a surprisingly easy decision when viewed in those terms.  Most SAAS products that likely would be implemented as SPAs do not care about public search engine access, and are only used by B2B customers where you can dictate a certain minimum standard in terms of browser versions (IE).&lt;p&gt;Everything else should be a traditional static web site with &amp;quot;decorative&amp;quot; JS, or &amp;quot;progressive enhancement&amp;quot;.</text></item></parent_chain></comment><story><title>JavaScript web apps considered valuable</title><url>http://molily.de/javascript-web-apps/</url></story>