<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>brundolf</author><text>JavaScript itself has gone through about a 10-year transition period from a toy language for writing quick scripts to a full-on general-purpose programming language. It didn&amp;#x27;t even have a &lt;i&gt;module&lt;/i&gt; system when Node launched.&lt;p&gt;So I strongly doubt the next 10 years will be anywhere near as tumultuous as the past 10. It&amp;#x27;s very possible that right now is just a much better time to be establishing a JS runtime.</text><parent_chain><item><author>paxys</author><text>When Node first released its biggest selling point was being able to reuse web APIs. It also filled in gaps for APIs that weren&amp;#x27;t standard in browsers. Then browsers started to add these APIs, and some of Node&amp;#x27;s implementations naturally diverged (aka the idiosyncrasies that you mention).&lt;p&gt;Deno has the advantage that they are starting from a clean slate without the burden of legacy APIs, but how long will that hold for?</text></item><item><author>maga</author><text>The often overlooked selling point of Deno that I find most compelling is the (re)use of web APIs. As a full-stack dev writing isomorphic code and libraries, dealing with ideosincracies of nodejs has been a pain.</text></item></parent_chain></comment><story><title>Deno 1.9</title><url>https://deno.com/blog/v1.9</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>bijection</author><text>You could argue that the apis in question are more mature now than when Node was first released.&lt;p&gt;Either way, if Deno is one day replaced by something else, say &amp;#x27;Done&amp;#x27; to keep the naming convention, that won&amp;#x27;t refute the use everyone will have gotten out of Deno in the mean time, in the same way that Deno doesn&amp;#x27;t refute the use everyone has already gotten out of Node.</text><parent_chain><item><author>paxys</author><text>When Node first released its biggest selling point was being able to reuse web APIs. It also filled in gaps for APIs that weren&amp;#x27;t standard in browsers. Then browsers started to add these APIs, and some of Node&amp;#x27;s implementations naturally diverged (aka the idiosyncrasies that you mention).&lt;p&gt;Deno has the advantage that they are starting from a clean slate without the burden of legacy APIs, but how long will that hold for?</text></item><item><author>maga</author><text>The often overlooked selling point of Deno that I find most compelling is the (re)use of web APIs. As a full-stack dev writing isomorphic code and libraries, dealing with ideosincracies of nodejs has been a pain.</text></item></parent_chain></comment><story><title>Deno 1.9</title><url>https://deno.com/blog/v1.9</url></story>