Show HN: Ezno, a TypeScript checker written in Rust, is now open source

Very cool! Congrats on the launch, even if it is very early.<p>Unsolicited feedback: I read the name an Enzo (n-zo) until I read the readme and realized it was Ezno (es-no).<p>Since in a previous post [0] you say you&#x27;re unsure on the name, Enzo could be a good one if this is a common mistake.<p>[0] <a href="https:&#x2F;&#x2F;kaleidawave.github.io&#x2F;posts&#x2F;introducing-ezno&#x2F;" rel="nofollow">https:&#x2F;&#x2F;kaleidawave.github.io&#x2F;posts&#x2F;introducing-ezno&#x2F;</a>

This is extremely early per the disclaimer at the top, like too early to even run most toy programs.<p>In general I&#x27;m kind of skeptical of the approach these rewrite in rust&#x2F;go projects are going. Maybe as wasm plugins for hot paths in existing tools, but it&#x27;s not clear to me that the full rewrites are where we want to be long term as a community.

I don&#x27;t know what it is about this name but I just can&#x27;t not read it as &quot;enzo&quot;.

Very cool! I&#x27;m curious, is this intended for dev tooling?<p>For example, I could see this (or something similar) being useful as the engine for a typescript language server that would be faster than the standard one<p>But if it&#x27;s not aimed at 1:1 with tsc, would it be intended more for something like swc[1]?<p>Or what would you expect people to use this for, besides just being a cool project to learn from?<p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;swc-project&#x2F;swc">https:&#x2F;&#x2F;github.com&#x2F;swc-project&#x2F;swc</a>

Discussion from when it was first announced: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32941613" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=32941613</a> (2022-09-22, 175 points, 98 comments).

The issue has always been that people start these projects, see just how big&#x2F;hard checking the whole of TypeScript is and don&#x27;t finish it.<p>It would be awesome if you finished it :]

I haven&#x27;t looked at the source, but the way to write one of these that&#x27;s fast is to use incremental computation. [0]<p>It tends to take a lot of RAM, but the speedups possible are 3-5 orders of magnitude in the projects I&#x27;ve studied.<p>Here&#x27;s a parallel C++ library to do so that requires relatively minor changes to the original algorithm. [1] [2]<p>I also believe it would be possible to develop a compiler framework to do the transformation mostly automatically, using an MLIR dialect.<p>[0] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Incremental_computing" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Incremental_computing</a><p>[1] <a href="https:&#x2F;&#x2F;dl.acm.org&#x2F;doi&#x2F;pdf&#x2F;10.1145&#x2F;3409964.3461799" rel="nofollow">https:&#x2F;&#x2F;dl.acm.org&#x2F;doi&#x2F;pdf&#x2F;10.1145&#x2F;3409964.3461799</a><p>[2] Source code: <a href="https:&#x2F;&#x2F;github.com&#x2F;cmuparlay&#x2F;psac">https:&#x2F;&#x2F;github.com&#x2F;cmuparlay&#x2F;psac</a>

Does this have tsconfig support, or is it only checking on a per-file basis so far?