News for hackers. Stuff that matters.
Re:Natalie – a work-in-progress Ruby compiler, written in Ru... by ricardobeat on Sunday September 24, 2023 @05:03PM (#37637177)
> I guess the standard Ruby compiler doesn't allow you to spit out binaries

Ruby is an interpreted language, programs are not compiled (except for the JIT compiler).

I wonder what makes this different from mruby[1] which seems to be very well supported for many years.

[1] https://mruby.org/

Re:Natalie – a work-in-progress Ruby compiler, written in Ru... by deaddodo on Sunday September 24, 2023 @05:39PM (#37637458)
If we're being honest, the only thing that differentiates an interpreted and compiled language is intention (design decisions that make one implementation versus the other easier) and what you choose to run the language through.

You can make almost any general purpose language "compiled", depending on how fat you're willing to make the runtime. And you can certainly create an interpreter/JIT VM for C/C++. It's not a question of possibility, but one of "why?".

Re:Natalie – a work-in-progress Ruby compiler, written in Ru... by runeblaze on Sunday September 24, 2023 @11:34PM (#37639430)
mruby is making ruby more lua-like (embeddable, etc.). If this project does AOT compilation well, we might be able to shave lots of interpreter overhead from Ruby for some applications.

I say some applications because there are still people using Ruby to write non-web things, and I doubt if this project will ever support Rails in the short term

Re:Natalie – a work-in-progress Ruby compiler, written in Ru... by timmorgan on Monday September 25, 2023 @12:54PM (#37646943)
Yeah, Rails would be a long ways off, if it ever happens at all. But I could see a use for compiled Sinatra, and that seems attainable in my lifetime. :-)