21–25 of 25 posts
The issue has always been that people start these projects, see just how big/hard checking the whole of TypeScript is and don't finish it. It would be awesome if you finished it :]
does TS even have a spec? I thought the type checking rules are basically "whatever tsc does"
Very cool! Congrats on the launch, even if it is very early. Unsolicited feedback: I read the name an Enzo (n-zo) until I read the readme and realized it was Ezno (es-no). Since in a previous post [0] you say you're unsure on the name, Enzo could be a good one if this is a common mistake. [0] https://kaleidawave.github.io/posts/introducing-ezno/
This is extremely early per the disclaimer at the top, like too early to even run most toy programs. In general I'm kind of skeptical of the approach these rewrite in rust/go projects are going. Maybe as wasm plugins for hot paths in existing tools, but it's not clear to me that the full rewrites are where we want to be long term as a community.
I think the HN title is pretty misleading.
Very cool! Congrats on the launch, even if it is very early. Unsolicited feedback: I read the name an Enzo (n-zo) until I read the readme and realized it was Ezno (es-no). Since in a previous post [0] you say you're unsure on the name, Enzo could be a good one if this is a common mistake. [0] https://kaleidawave.github.io/posts/introducing-ezno/
Naming still remains the hardest programming problem ...
Does this have tsconfig support, or is it only checking on a per-file basis so far?