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

Why not build on top of Java? #15

Closed
dapz opened this issue May 5, 2012 · 3 comments
Closed

Why not build on top of Java? #15

dapz opened this issue May 5, 2012 · 3 comments

Comments

@dapz
Copy link

dapz commented May 5, 2012

There are many java matrix libraries available. Why not simply build on top of one of those?

Yes, now you must use JRuby instead of C Ruby. However, you can build the library more quickly, gain critical mass for later building the CRuby version, etc.

@translunar
Copy link
Member

If this is something you're interested in doing, you should do it. None of us know Java, though, and we do know C. So there's that. =)

@dapz
Copy link
Author

dapz commented May 9, 2012

I don't really know Java either. But I don't really have to; effectively this reduces the problem to just providing thin wrappers around Java libraries.

This saves a lot of time, I think (in terms of getting a functional, performant library up.)

@dapz dapz closed this as completed May 9, 2012
@translunar
Copy link
Member

This is the approach we're taking with the distribution gem and much of statsample, I believe. However, we want the interface for the different matrix types to be the same, and that's more complicated.

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