LeuGim said:
> For me it's allowing to write code compact and looking intuitively, and
> having many solutions to the same task, at programmer's choice. Something
> characteristic for Ruby, but even more so for Nim.
Completely agree! I haven't felt so liberated using a programming language
sin
I love the simplicity of the transpiler and the fast compilation time. The cool
features are icing.
I like Nim because:
* I can use it to unify, typify and abstract code between different target
languages.
* At the same time Nim is a full native code systems programming language.
* NimScript lets me write mundane tasks which would otherwise written in
another (scripting) language.
* By
_wulfklaue:_ Predominance of negative opinions over positive ones is common,
not only in this case, and for a simple reason: when people are content with
something, they have nothing to say against, and they mostly are silent, and
when they annoyed or uncomfortable with something, then they expr
Partial casing is simply the next logical step, IMHO. As our editors grow
smarter and smarter they should allow us to present the code in the way we're
most comfortable with. This means the freedom to render `fooBar` as `foo_bar`
instead. What's necessary to accomplish this goal? `fooBar` has to
cjxgm: Your the first person who i have ever seen to give a real world example
as to why Partial casing can be useful. Seen so many topics in reddit etc where
people express frustrated by the free casing/merger but nobody ever provides a
example as to why it can be useful. I only see the negativ
What I liked so far:
* * *
* **Express the intention of "base" instead of "override".**
We have `override` keyword in C++ and `@Override` annotation in Java, to
express our intention of "overriding the base function instead of creating a
new base function/overloading/overwriting". That's j
For me, I was looking for
* a python-like syntax (fast-to-write/easy-to-read coding)
* c-like speed
* GC to handle memory allocation/de-allocation
For me it's allowing to write code compact and looking intuitively, and having
many solutions to the same task, at programmer's choice. Something
characteristic for Ruby, but even more so for Nim.
Yet its Delphi's roots (which I think gave Nim much of its elegance).
Nim is great because it has this underdog spirit taking on all and everyone, it
is down to earth , not overly academic and most of it is fun.
The excitement feels similar to when I was changing from Fortran77 to Turbo
Pascal , if I recall that correctly. :P
Fast / Low memory usage ( compared to competitors ) Compiles to a single binary
Relative clean syntax Macro support Hardware support Flexible
In other words, all of GoLang its features but better / more flexible / more
options / less limitations.
Since most posts here are basically about what people don't like (me included)
and questions about things that don't work, I would like to ask, what you like
the most about Nim. What is the reasons you believe in Nim. Or simply what part
of the language or the standard library do you think is th
12 matches
Mail list logo
