Comment by zdw
2 days ago
This compiles to native binaries, as opposed to deno which is also in rust but is more an interpreter for sandboxed environments?
2 days ago
This compiles to native binaries, as opposed to deno which is also in rust but is more an interpreter for sandboxed environments?
Oxc is not a JavaScript runtime environment; it's a collection of build tools for JavaScript. The tools output JavaScript code, not native binaries. You separately need a runtime environment like Deno (or a browser, depending on what kind of code it is) to actually run that code.
Deno is a native implementation of a standard library, it doesn't have language implementation of its own, it just bundles the one from Safari (javascriptcore).
This is a set of linting tools and a typestripper, a program that removes the type annotations from typescript to make turn it into pure javascript (and turn JSX into document.whateverMakeElement calls). It still doesn't have anything to actually run the program.
Deno uses V8, which is from Chrome. Bun uses JavaScriptCore.
Ah, yeah. Easy mistake
I'm going to call it: a Rust implementation of JavaScript runtime (and TypeScript compiler) will eventually overtake the official TypeScript compiler now being rewritten in Go.
? Most JavaScript runtimes are already C++ and are already very fast. What would rewriting in Rust get us?
1 reply →
In popularity or actually take over control of the language?
1 reply →
If you want native binaries from typescript, check my project: https://tsonic.org/
Currently it uses .Net and NativeAOT, but adding support for the Rust backend/ecosystem over the next couple of months. TypeScript for GPU kernels, soon. :)
No, it it a suite of tools to handle Typescript (and Javascript as its subset). So far it's a parser, a tool to strip Typescript declarations and produce JS (like SWC), a linter, and a set of code transformation tools / interfaces, as much as I can tell.