Hacker News Reader

Comment by baggy_trough | Hacker News Reader

If you know you're going to rewrite the thing in a new language, then why push to include it in ruby now?

We didn't push to upstream now, we were invited to upstream in CRuby and we accepted the invitation. As for the Rust rewrite, we just started to work on the prototype, and no decision had been made. The ticket linked in this thread is me essentially asking the Ruby core devs for permission to do so. We wanted to give everyone an opportunity to chime in.

Not sure what to tell you. Things don't aways happen in the most optimal order in the real world, sometimes plans change, but I'm fairly confident that we can make this work well.

Thse are all not only solved problems, but solved extremely well. Rust is a bad solution to this problem.

You should be using dynasm https://luajit.org/dynasm.html instead of plain C.

How does that make graph transformations easier and avoid issues with memory management related to those? I tried looking in the docs at your link to see (because it looks a lot more like a syntax extension for an assembler than anything that helps with the problems the author noted), but the page notes,

> Sorry, right now there is no proper documentation included other than some Examples and of course the source code. The source is well documented, though (IMHO).

and the example doesn't seem to have anything relevant to the problems identified above.

Reply on news.ycombinator.com