[cb321]

Do you have any specific libraries that you are missing? The packages list [1] has almost 1600 packages.

Also, the FFI in Nim is basically just declaring some C function as a `proc`. So, wrapping existing C libraries is as easy as Cython for Python. You can even jump start things by running `c2nim` on a header file.

[1] https://github.com/nim-lang/packages

[tutfbhuf]

We use the Neo4j graph database quite extensively, so a Neo4j driver / client SDK would be nice. And for intra service messaging we need a google cloud pubsub client library.

[cb321]

Not sure how well it works (and I have no setup to test), but there is this [1]. It's pretty old and Nim has evolved quite a bit in the last 4 years. It probably doesn't compile, but it might not be hard to spruce it up (not that this would be a great "intro project"). { EDIT: Open source is often pretty thankless. It might be that if you asked nicely of that repo owner that he would do the sprucing! :-) }

I know there are a few different protobuf impls floating around. Not sure how much google pubsub needs beyond that. It's probably not so far away. Maybe you can be the one to do the pubsub wrapper. :-) (I'm only trying to encourage, not enlist/conscript.)

[1] https://github.com/cmacmackin/nim-neo4j

[tutfbhuf]

I appreciate your effort, I also have a hacker spirit / hands on mentality for my own hobby projects. But in this case I simply cannot "sell" it to my team. We really need something already production ready with community support behind it.

[cb321]

Oh, and, FWIW, most of the time Nim code runs much faster than Go. More like C/C++/Rust speed.

[cb321]

Ok. Well, then...maybe your next hobby project should be in Nim. :-)

[tutfbhuf]

Yup, I'll consider that.