Should we drop support for mruby?
mruby is not really designed to be installed globally on the system, but configured and compiled into projects.
While mruby is designed to be compiled into projects it does have potential when all you need is specific functionality without all the overhead of ruby. All you would need to do is decide what you need and pick the mrbgems.
Out of curiosity would it be possible to create mruby binary that contained mruby + mrbgems + mruby script(s) as a single static binary? If so would it be possible to get that in ruby-install, or is that too out of scope for this project?
+1 on keeping mruby. I think it has potential.
@grimnight mruby could use some sort of ./configure script to automate the build process.