3 ms·
This is what it is for me: Objective-C -> Nim (can compile to ObjC, calls methods directly without overhead) Python -> Nim (Nim is a super fast python that
by treeform 7y ago
This is what it is for me:
Objective-C -> Nim (can compile to ObjC, calls methods directly without overhead)
Python -> Nim (Nim is a super fast python that prevents typos)
Ruby -> Nim (Nim is better in every-way)
JavaScript -> Nim (compiles to plain JS (if you need talk to legacy JS libs like most people) or WASM (if you just want speed))
C/C++ -> Nim (Can compile to C++, calls methods directly without overhead)
Basically...
- TeddyDD 7y agoYeah, Nim has impressive coverage of targets. I dislike almost everything about Nim: the syntax, complexity, weird case insensitivity, documentation, community, package manager...Yet this trait alone makes Nim worth leaning for me.
- jaco8 7y agoHmmm , cannot agree with you here: syntax is great and easy to learn, complexity crockable in a day or two, documentation looks good and actively being worked on , community is very welcoming and knowledgeable, package manager nimble is easy to use. Have you actually tried yet ?
- aredirect 7y agoThere's a huge effort on the documentation part recently, and the community is kind. Any specific pain points?