Feature #18265: Self-contained one-binary feature which discuss on ruby kaigi 2021 day 2, 《 Ruby Committers vs the World / CRuby Committers》

• Status: Open
• Assignee: -
• Target version: -

[zw963 (Wei Zheng)]

https://www.youtube.com/watch?v=zQnN1pqK4FQ

Yes, what i said is this.

1. Go-language supports to make self-contained one-binary.
2. Is it useful for ruby?

I personal propose add this feature into ruby 3.X in the future, i consider this is a killer
advantage compare to others dynamic language.

And, this feature is very important for distribute code to the third party.(e.g. client) for two reason:

1. distribute is easy.
2. for protect code change unexpectly by client

in fact, my friend switch from ruby to go recent days, the only reason is, it could not find out
a usable solution to distribute code to our client safely.

Because i could not find out a mature similar issue, so, just create this for discuss.

BTW: maybe not so useful, Emacs editor since version 28 can native compilation of Elisp files which has greatly improved performance and start-up time, i don't know if this tech can be borrow from there for ruby.

anyway, i consider both are similarities, i hope that can help.

Following is some links come from Andrea Corallo, the emacs native compilation maintainer.

https://akrl.sdf.org/gccemacs.html
https://akrl.sdf.org/Kludging_LPC_2020.pdf

Hope there have useful info for AoT ruby .rb source code into .rbn(rb native, as .el compile to .eln) use libgccjit.

[zw963 (Wei Zheng)]

• Subject changed from One-bianry feature which discuss on ruby kaigi 2021 day 2, 《 Ruby Committers vs the World / CRuby Committers》 to Self-contained one-bianry feature which discuss on ruby kaigi 2021 day 2, 《 Ruby Committers vs the World / CRuby Committers》

[zw963 (Wei Zheng)]

• Description updated (diff)

[Eregon (Benoit Daloze)]

FYI, MRuby supports this. Of course it just embeds the bytecode in the binary, no actual AOT compilation of Ruby code.

Also there are various gems which make this possible for CRuby, notably https://github.com/pmq20/ruby-packer, although I'm not sure how easy/hard it is to use them.

Personally I'm not sure I see the advantage of one executable vs one archive with a clear executable inside.
One executable forces using a virtual file system and potentially extracting .so files in a temporary directly on every execution
(e.g. dlopen()/native library deps need a real file on the filesystem, and that's needed for C extensions which can't easily be statically-linked),
vs the archive working much more similarly to regular Ruby installations.

[duerst (Martin Dürst)]

• Subject changed from Self-contained one-bianry feature which discuss on ruby kaigi 2021 day 2, 《 Ruby Committers vs the World / CRuby Committers》 to Self-contained one-binary feature which discuss on ruby kaigi 2021 day 2, 《 Ruby Committers vs the World / CRuby Committers》

• Fixed typo in Subject

• When proposing a feature, please describe the feature in the text here, not just by reference (e.g. to a Youtube video).

[zw963 (Wei Zheng)]

• Description updated (diff)

[zw963 (Wei Zheng)]

• Description updated (diff)

[zw963 (Wei Zheng)]

• Description updated (diff)

[zw963 (Wei Zheng)]

duerst (Martin Dürst) wrote in #note-4:

• Fixed typo in Subject

• When proposing a feature, please describe the feature in the text here, not just by reference (e.g. to a Youtube video).

Updated, so there is exists more describe for now.

for that youtube video, except copy the video content, i can't do more, because I can't understand Japanese