Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
shehackedyou opened this issue Jan 11, 2024 · 3 comments

Comments

@shehackedyou
Copy link

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
Copy link
Owner

ohler55 commented Jan 11, 2024

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
Copy link
Author

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
Copy link
Owner

ohler55 commented Jan 13, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants