<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>simlevesque</author><text>&amp;gt; Ecosystem is still worse, which is IMO all that matters at this point.&lt;p&gt;Matters for what ? Doing every type of app ? Yeah, that&amp;#x27;s blocker.&lt;p&gt;But it doesn&amp;#x27;t really matter. Every language ecosystem that succeeds starts off lacking things.&lt;p&gt;Personally I prefer starting with it early and be part of that ecosystem.</text><parent_chain><item><author>lucasyvas</author><text>Ecosystem is still worse, which is IMO all that matters at this point.&lt;p&gt;ts-node is good enough to stick to Node for now if you want TypeScript. I don&amp;#x27;t think the rest of Deno is that compelling, although I would probably switch to Deno once its Node compat is awesome since it is a more compelete package out of the box than Node is.&lt;p&gt;Deno&amp;#x27;s battle is that it is an incremental improvement, and competing JS runtimes is quickly become the new JS web framework meme alternative (Bun, Boa, Node, Deno)</text></item><item><author>k__</author><text>Half-OT:&lt;p&gt;Anyone got experience with switching from Node.js to Deno?&lt;p&gt;What&amp;#x27;s better with Deno? What&amp;#x27;s still worse?</text></item></parent_chain></comment><story><title>Deno 1.26 Release Notes</title><url>https://deno.com/blog/v1.26</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>Rapzid</author><text>ts-node is great. Proper ESM support landed over the summer. All my new projects at work are module type now.&lt;p&gt;I use ts-node with the optional SWC compiler which works great with pretty darn fast startup times. SWC can handle TypeScript experimental decorators including emitting metadata, so not losing out on anything with it ATM.</text><parent_chain><item><author>lucasyvas</author><text>Ecosystem is still worse, which is IMO all that matters at this point.&lt;p&gt;ts-node is good enough to stick to Node for now if you want TypeScript. I don&amp;#x27;t think the rest of Deno is that compelling, although I would probably switch to Deno once its Node compat is awesome since it is a more compelete package out of the box than Node is.&lt;p&gt;Deno&amp;#x27;s battle is that it is an incremental improvement, and competing JS runtimes is quickly become the new JS web framework meme alternative (Bun, Boa, Node, Deno)</text></item><item><author>k__</author><text>Half-OT:&lt;p&gt;Anyone got experience with switching from Node.js to Deno?&lt;p&gt;What&amp;#x27;s better with Deno? What&amp;#x27;s still worse?</text></item></parent_chain></comment><story><title>Deno 1.26 Release Notes</title><url>https://deno.com/blog/v1.26</url></story>