←back to thread

Nim 2.2.6

(nim-lang.org)
159 points xz18r | 1 comments | 31 Oct 25 14:15 UTC | HN request time: 0s | source
Show context
treeform ◴[31 Oct 25 15:55 UTC] No.45773510[source]▶
Thank you for working on the Nim Compiler. This is great. Another great release. The Nim Compiler continues to move forward.

Thank you very much to everyone who has contributed to the development of this superior language. Nim Compiler continues to be one of the most wonderful languages I have worked with. With the speed of C and the simplicity of Python, it has allowed me to write a lot of cool software.

I do not know where I would be if Nim did not exist in my life.

replies(2): >>45773553 #>>45773671 #
pansa2 ◴[31 Oct 25 16:07 UTC] No.45773671[source]▶
> with the simplicity of Python

So, not simple at all, then? Python is a very complex language hiding behind friendly syntax.

Do you just mean “with the syntax of Python”? Or does Nim’s similarity to Python go more than skin-deep?

replies(7): >>45773739 #>>45773919 #>>45774050 #>>45774960 #>>45775492 #>>45775901 #>>45778861 #
1. netbioserror ◴[31 Oct 25 16:33 UTC] No.45773919[source]▶
In practice, it means that unlike most native-compiled languages, if you want a data-oriented approach without having to worry about system details at all, you can do that. Your program will still be strongly typed, but you're not obligated to worry about allocation, reference vs value semantics, ownership, or initialization details. For programs that shouldn't have to worry about those details, the Nim team has done a lot of work to make sure the language gets out of the way and lets you process data. Then, you get a fast binary comparable to the results you'd get from C++ (with a lot more effort).

In buzzword-speak, it's easy to write programs composed of nearly pure business logic while getting C++-level performance.