3 ms·
What do you mean by "production ready" here exactly? In a web browser context, the JS engine is expected to have a high performance optimising JIT compiler. Do
by mort96 7mo ago
What do you mean by "production ready" here exactly? In a web browser context, the JS engine is expected to have a high performance optimising JIT compiler. Do the existing Rust JS engines have that?
- swiftcoder 7mo agoI honestly don't know, but they do say "production ready" on their marketing pages, so... For an example of what I mean, see JetCrab: https://jetcrab.com https://jetcrab.com
- mort96 7mo agoThat page says: > Complete JavaScript execution pipeline from source code parsing to bytecode execution. So it's a bytecode interpreter, not a JIT. It might still be production ready for a bunch of use cases. I may use it as a scripting layer for some pluggable piece of software or a game. I wouldn't consider it appropriate for a "production ready web browser" which intends to compete with Firefox and Chrome. EDIT: Also for some reason all its components are called v8_something? That's pretty off putting, you can't just take another project's name like that.. and from the author's Reddit comments it seems to be mostly AI slop anyway. I'm guessing Claude wrote the "production ready" part on the website, I wouldn't trust it.
- CryZe 7mo agoThis doesn't implement a JS engine, it's just a wrapper around boa.
- 8NNTt8z3QvLT8tp 7mo agoThere's something to be said for the security benefits of not having a JIT though. Especially if you've used Rust for the engine you should have pretty solid security.