Might consideration be given to including Ruby executables with SU installs?
See Async download a file?. Some of the discussion got ‘off-topic general’. Main idea was about tasks that did not require use of SU objects being sent to a spawned Ruby process.
Being able to do so may allow people to use gems in the external processes, which removes the ‘shared object space’ issue when loaded within SU.
Not that familiar with macOS, but from a Windows perspective, along with making a change like this, it would be a good time to change the embedded Ruby setup:
- Use ‘manifested’ dlls.
- Connect correctly to a ‘–user-install’ gem directory.
- The folder layout could be changed to more closely match a normal Windows Ruby install.
@kengey and I both made use of checking pid status of the external processes. I may investigate in what ways an external Ruby process can be set up to act like a REST server…
Spawned processes need very good code controlling them, and they can certainly be improperly used. Regardless, as everything becomes more distributed, this addition might be very helpful for complex plugins.
@tt_su, any thoughts?