Live data from Hacker News

HolyJit: A New Hope

blog.mozilla.org

41–50 of 219 posts

Re: HolyJit: A New Hope

#41

First thought was: "Is this another Terry Davis language/framework?"[1] No, no it is not. I would suggest changing the name from HolyJit to anything else. [1] https://en.m.wikipedia.org/wiki/TempleOS

But it sounds like "holy shit" LOL. You know what else is funny? Farts!

Well you know, as Louis C.K. once said, you don't have to be smart to laugh at farts, but you have to be stupid not to.

Re: HolyJit: A New Hope

#42
post #8

I'm not sure as to what is fundamentally different about this JIT-compiler (except for the awesome name of course) Is it basically just a Rust rewrite which also tries to reduce the complexity of their current just-in-time compiler? Edit: By calling it "just" a Rust rewrite, I'm not implying that's a simple undertaking, even moreso considering the complexity of modern JS engines.

Name reminds me of TempleOs's HolyC language...

Inb4 HolyOS, HolyBrowser, HolyKernel

Re: HolyJit: A New Hope

#44
post #40

I'm not sure as to what is fundamentally different about this JIT-compiler (except for the awesome name of course) Is it basically just a Rust rewrite which also tries to reduce the complexity of their current just-in-time compiler? Edit: By calling it "just" a Rust rewrite, I'm not implying that's a simple undertaking, even moreso considering the complexity of modern JS engines.

Basically, instead of manually writing assembly fragments, they want to reuse annotated interpreter code, thus ensuring both correctness and safety for JIT-generated code, while reducing the redundancy. The rustc compiler is used to generate assembly fragments for the JIT, directly out of the interpreter code. It seems like a worthwhile endeavor.

Your explanation is much better than what I can read in the blog post.

Re: HolyJit: A New Hope

#45
post #39

For what it's worth, the name is obviously a pun and a small wink to the Graal VM [1]. Not sure there's any intention to reference TempleOS's HolyC. [1] https://github.com/graalvm/

Hate to be a downer but I don't get the pun at all.

Re: HolyJit: A New Hope

#46
post #25

Can we just drop the JS VM and embed some nicer VM (JVM, DartVM) instead?

Yes, once you convince everyone to drop the thing we have that works and implement the thing we don't have that doesn't work. In short: you complain as though it were an easy change to make.

He/she is right though, just wait when WebAssembly gets more mature.

I bet all those plugins will be back.

Re: HolyJit: A New Hope

#47
post #39

For what it's worth, the name is obviously a pun and a small wink to the Graal VM [1]. Not sure there's any intention to reference TempleOS's HolyC. [1] https://github.com/graalvm/

Hate to be a downer but I don't get the pun at all.

Graal is an archaic spelling of grail.

Re: HolyJit: A New Hope

#48

Can we just drop the JS VM and embed some nicer VM (JVM, DartVM) instead?

Thanks to WebAssembly there are already porting attempts for quite a few runtimes, just let it mature a bit more and we will get the revenge of plugins.

Re: HolyJit: A New Hope

#49
post #39

For what it's worth, the name is obviously a pun and a small wink to the Graal VM [1]. Not sure there's any intention to reference TempleOS's HolyC. [1] https://github.com/graalvm/

Hate to be a downer but I don't get the pun at all.

https://en.wikipedia.org/wiki/Holy_Grail , "Graal" is an archaic spelling of "Grail".

Re: HolyJit: A New Hope

#50

First thought was: "Is this another Terry Davis language/framework?"[1] No, no it is not. I would suggest changing the name from HolyJit to anything else. [1] https://en.m.wikipedia.org/wiki/TempleOS

But it sounds like "holy shit" LOL. You know what else is funny? Farts!

Mozilla's image library was called libpr0n back in the day, so you might say there is some form.
Post reply on HN