<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>npsimons</author><text>Exactly; those of us &amp;quot;vituperating priests&amp;quot; who rail against JavaScript abuse are mostly complaining about things like plain text (or even text plus photos) &lt;i&gt;requiring&lt;/i&gt; JavaScript. You want to create some whiz bang new thing that needs Turing completeness? Go to town with JavaScript. You want to require enabling a possible malware vector and chew through computer resources like they&amp;#x27;re candy just to read a few paragraphs of text? Forget you, I&amp;#x27;ll keep browsing. And so will crawlers, so you&amp;#x27;ll never get linked. Attention is scarce, information is not - do the math.</text><parent_chain><item><author>glesica</author><text>&amp;quot;And most importantly: Don’t be ashamed to build 100% JavaScript applications. You may get some incensed priests vituperating you in their blogs. But there will be an army of users (like me) who will fall in love with using your app.&amp;quot;&lt;p&gt;This statement needs a huge, HUGE caveat that you should only be building 100% JavaScript apps in situations where doing so &lt;i&gt;makes sense&lt;/i&gt;. For example, I find the new Blogger &amp;quot;web app&amp;quot; infuriating. I shouldn&amp;#x27;t have to stare at a loading screen to read a half-dozen paragraphs of text, that&amp;#x27;s just stupid. Just serve the HTML. No one is going to &amp;quot;fall in love&amp;quot; with your app if your app shouldn&amp;#x27;t exist in the first place because the old-school solution provided a superior experience.</text></item></parent_chain></comment><story><title>Progressive Enhancement Is Dead</title><url>http://tomdale.net/2013/09/progressive-enhancement-is-dead/</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>diminish</author><text>i m still opening a dozen tabs and reading them whenever i want, unfortunately most newer js only web  blogs such as inc mobile, end up having a lot of errors and white pages..&lt;p&gt;i understand your newly found js excitement with your full ember.js app, but do&amp;#x27;nt forget the lessons from java the browser plugin and flash.&lt;p&gt;1. ok you re real time, but don&amp;#x27;t assume i m watching your site like a tv&lt;p&gt;2. dont consume my precious cpu power..  otherwise app throttling will come to browser tabs..&lt;p&gt;3. dont end up in lots of clientside errors due to various problems, including local storage.. twitter mobile client is an abysmal example where tweets are lost on screen and inc mobile is another with empty ehite pages</text><parent_chain><item><author>glesica</author><text>&amp;quot;And most importantly: Don’t be ashamed to build 100% JavaScript applications. You may get some incensed priests vituperating you in their blogs. But there will be an army of users (like me) who will fall in love with using your app.&amp;quot;&lt;p&gt;This statement needs a huge, HUGE caveat that you should only be building 100% JavaScript apps in situations where doing so &lt;i&gt;makes sense&lt;/i&gt;. For example, I find the new Blogger &amp;quot;web app&amp;quot; infuriating. I shouldn&amp;#x27;t have to stare at a loading screen to read a half-dozen paragraphs of text, that&amp;#x27;s just stupid. Just serve the HTML. No one is going to &amp;quot;fall in love&amp;quot; with your app if your app shouldn&amp;#x27;t exist in the first place because the old-school solution provided a superior experience.</text></item></parent_chain></comment><story><title>Progressive Enhancement Is Dead</title><url>http://tomdale.net/2013/09/progressive-enhancement-is-dead/</url></story>