11–20 of 25 posts
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/
[0] https://enso.org
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/
I think Enso is already taken by a YC company [0]. Could get confusing. [0] https://enso.org
It’ll have different associations to different people. Good reason to just add to it.
It tends to take a lot of RAM, but the speedups possible are 3-5 orders of magnitude in the projects I've studied.
Here's a parallel C++ library to do so that requires relatively minor changes to the original algorithm. [1] [2]
I also believe it would be possible to develop a compiler framework to do the transformation mostly automatically, using an MLIR dialect.
[0] https://en.wikipedia.org/wiki/Incremental_computing
[1] https://dl.acm.org/doi/pdf/10.1145/3409964.3461799
[2] Source code: https://github.com/cmuparlay/psac
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/
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 :]
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"
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.
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"
Some pointers from this stackoverflow discussion:
https://stackoverflow.com/questions/52148566/is-the-typescri...