Closed brandur closed 8 years ago
Carl pinged me offline about this one, and it looks like this project isn't very well maintained right now. It seems that the project was largely kicked off while Ruby's process interface was quite a bit worse than it is today. One major feature that it still does have is the #communicate
method, which acts as an asynchronous pipe by combining a pipe with select. Closing this issue out for now.
This is a suggested improvement, so feel free to close it out as such.
Coming into Subprocess with fairly naive eyes and reading the README, I find myself left not quite grasping why I should be using the library. I believe that the main selling point is that it provides a better interface for communicating with a subprocess compared to the various Ruby primitives, but I'm not completely sure.
I suspect that the reaction of a good portion of developers these days (including me) would be that the a slightly improved API isn't the added weight of a new dependency. It might be worthwhile to include a list of Subprocess' strengths in the
README
for newcomers to the project.