<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>xixixao</author><text>Related but more high level, I think we should have language sets instead of single languages with simpler interop and shared infra: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;xixixao&amp;#x2F;8e363dbd3663b6729cd5b6d74dbbf9d4&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;gist.github.com&amp;#x2F;xixixao&amp;#x2F;8e363dbd3663b6729cd5b6d74dbb...&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>TypeScript as fast as Rust: TypeScript++</title><url>https://zaplib.com/docs/blog_ts++.html</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>simjnd</author><text>Not sure if you&amp;#x27;re familiar with or heard about AssemblyScript [1]. It sounds like the goal you are trying to achieve, but with a saner approach: create a TypeScript-like language that compiles to WebAssembly. This means it gives you native access to SIMD, and eventually even threads! All while avoiding the overhead of learning a new language (well there are still some gotchas since it is actually a new language, but very close).
No need to think about whether you need to optimize X function or manually manage memory somewhere, and still get the awesome performance of Wasm.&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.assemblyscript.org&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.assemblyscript.org&amp;#x2F;&lt;/a&gt;</text><parent_chain></parent_chain></comment><story><title>TypeScript as fast as Rust: TypeScript++</title><url>https://zaplib.com/docs/blog_ts++.html</url></story>