Hacker News Reader

While I'm not super familiar with the scientific computing field, I can say that Nim needs everyone's help in building the library ecology. Right now, Nim seems to be in the wrap-all-the-things! mode. You can see that most of the available packages are bindings to existing libraries. I'm not sure this is a bad thing. And I don't think it has anything to do with anything other than Nim's currently small community.

View on HN

I don't see a problem with that. Since Nim compiles to C, it's only natural for people to take advantage of existing C libraries.

I certainly agree.

I haven't dived deep enough to figure out if integration with existing C/C++/Fortran libraries works out-of-the-box, or whether you have to setup bindings a la Python. If it works out-of-the-box, my question is moot, especially if two-way interoperability with Nim code is seamless.

You have to set up bindings but it is as simple as it could possibly be to do by hand, and there is a c2nim program to help.

Reply on news.ycombinator.com