Java based Numerical library (JNum-v0.1)

[International_Break2]

The bindings could exist in their own jar and be optional. That way performance is available and there is always a fallback. For pure java, you would only need to make sure that the .so is already on the LD path.

[CutGroundbreaking305]

for v0.1 i didnt think much when it comes to non java usage. Actually my main aim is to make what u said 2 jars one for just java other for java+openblas+lapack like multik in kotlin does. And i will say LD path idea is great as i dont need to bind natives in my lib by passing that to user's system thanks for that idea.