Out of curiousity would anything have been lost or gained by using ABI, or FFI, or *.SO over the current API method of directly calling in the Ruby C file headers?

ohler55 / agoo

A High Performance HTTP Server for Ruby

MIT License

912 stars 39 forks source link

Out of curiousity would anything have been lost or gained by using ABI, or FFI, or *.SO over the current API method of directly calling in the Ruby C file headers? #129

Closed shehackedyou closed 3 months ago

shehackedyou commented 10 months ago

I'm curious because I have been watching this project a long time, experimenting with it to learn more about Rack, and I am interested in doing some of my own direct work with the Ruby source. And would it just be advantageous to package Ruby headers and source, or compile it into a *.so? FFI?

Are there any major drawacks to any of these proposed solutions?

ohler55 commented 10 months ago

When I started out there was only one real option. That is no longer true but I haven't spent the time to compare other choices. I would be interested in anything you find out though.

shehackedyou commented 10 months ago

Okay, yeah I plan to experiment with each and see the results then. I will inform, Ill write about it and send you the link.

I appreciate the time you took to respond to me. Really love this project, it changed the way I think about Rack and Rails so much. Was a huge breakthrough for me; thanks for that.

ohler55 commented 10 months ago

I am curious, how did it change your views on Rack and Rails?