Re:Show HN: Lua/LuaJIT with C/C++/Java/JavaScript syntax
by sifoobar on Sunday December 30, 2018 @10:49PM
(#18792882)
Just noting that JIT means speculating from what you've seen so far, what I'm doing is proving invariants and removing redundancy at compile time. Which means more predictable performance, since the code stays the same once it starts running; and a less complex implementation, since there's no need to de-optimize anything.
The reason I'm tracing is that it's the only way I've found to prove anything of value in such a formless language; even Lisp knows which arguments belong to which function call, in Forth that depends on what came before.
And it fits well with an interpreted language, since a slow compile often defeats the purpose of compiling in the first place. The tracing I've implemented so far is instant in comparison.
Re:Show HN: Lua/LuaJIT with C/C++/Java/JavaScript syntax
by sifoobar on Sunday December 30, 2018 @05:36PM
(#18791758)
Agreed; C, Forth & Lisp are all acquired tastes.
Which is fine, one size never fits all.
Just wanted to mention some alternatives to LuaJIT, since I don't think it's a viable way forward for languages of this scale.
Likewise!
Best wishes !