5 ms·
To me this is more of an argument against. Although Python was my first language, I've had my share of burnouts because of its lack of types and difficulties in
by loxs 6y ago
To me this is more of an argument against. Although Python was my first language, I've had my share of burnouts because of its lack of types and difficulties in refactoring big code-bases.
- Tiberium 6y agoDon't be misleaded - the only thing Nim really has from Python is the off-side rule (indentation). Nim is statically typed and compiled to native binaries
- arc776 6y agoYeah I should have stressed that it's just the productivity that matches Python, not the operation. As you say it's similarity is only skin deep with significant whitespace. In terms of use I find it feels a lot like a better Pascal but with powerful metaprogramming.
- arc776 6y ago> I've had my share of burnouts because of its lack of types and difficulties in refactoring big code-bases. Nim is strongly, statically typed. Also, I agree and aside from performance it's why I started using Nim instead of Python for my gamedev hobby. Dynamic typing isn't good for large projects. Nim has great type inference though, so you get the readability of Python but with strong compile time type guarantees. Eg; type SpecialId = distinct int # This int is now type incompatible with other ints proc handleId(id: SpecialId) = # ... do something with id.
- nimmer 6y agoNim has productivity, expressiveness and readability that matches Python. Not the dynamic typing.