Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Nim (formerly Nimrod) 0.10.2 released

nim-lang.org

Post reply on HN
Print view View original

81–90 of 149 posts

Re: Nim (formerly Nimrod) 0.10.2 released

#81

Post by pcwalton »

dom96 wrote: post #78
pcwalton wrote: post #75

Earlier quoted context omitted.

That isn't an advantage, IMHO. rustc generates LLVM IR, which allows it to take advantage of essentially all the same optimization passes that clang does. Generating LLVM IR instead of C has some advantages—debug information can be made more precise, precise aliasing metadata for optimization can be added to the output, accurate garbage collection is possible, there's no need to go through the C parser and semantic a…

Perhaps it's not an advantage, but it certainly is not a disadvantage. An advantage that I can think of is portability as well as easier interfacing with C libraries.

Almost all systems that matter have an LLVM port these days, so portability isn't really an issue in practice (though sometimes C can help with microcontrollers, etc.) Game consoles in particular are all x86 or PPC these days. Easier interfacing with C libraries is a fair point, although you still have to figure out how the two languages' type systems interact and presenting good error messages can be a pain if you're relying on the C compiler to do semantic analysis.

Re: Nim (formerly Nimrod) 0.10.2 released

#82

Post by dom96 »

avz wrote: post #70
gokr wrote: post #57

Earlier quoted context omitted.

Wow, I just have to reply! Which one of these do you prefer: echo("Hello") echo "Hello" "Hello".echo "Hello".echo() Or something different?

This: cout beats all of the above by a wide margin. It's essentially an ASCII-art ideographic representation of what the computer is supposed to do.

    proc `
There you go :)

Re: Nim (formerly Nimrod) 0.10.2 released

#83

Post by [deleted] »

klibertp wrote: post #49
ebbv wrote: post #33

Earlier quoted context omitted.

First, I have never and probably would never use the word "beautiful" to describe any code. I purposefully chose "clean and nice" in my last comment. As far as the new crop of languages go, I think Rust and Go both offer better refinements of older languages than Nim does. If you're going to come out with a new language, the syntax of it should be cleaner and easier to read than what you are replacing (in this case,…

I downvoted you because what you say is both wrong and harmful. This: > I find this language pretty ugly. And [...] that's enough reason to not use it. is the worst possible way of choosing a language to use. It's simply stupid to dismiss languages which may suit your current problem on the grounds of aesthetics. I can't imagine a single situation where "disregarding technical advantages" of a language would be even…

[deleted]

Re: Nim (formerly Nimrod) 0.10.2 released

#84

Post by daveroberts »

themartorana wrote: post #9

All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…

Go and Rust and included in the Computer Language Benchmark game: http://benchmarksgame.alioth.debian.org/

Nim, and many of the other interesting languages mentioned in this thread are not.

I'm not sure if this is a cause or effect.

Re: Nim (formerly Nimrod) 0.10.2 released

#85

Post by bluecalm »

gokr wrote: post #57
ebbv wrote: post #39

Earlier quoted context omitted.

Brief is not the same as lazy. I personally find comments that say what they mean to say in a short amount of text much more useful than ones that go on for paragraphs without saying anything new. I strive for brevity. I revised the one you responded to so you may want to check that now. As far as more details of what I don't like about Nim, that would have been easy to ask directly; I find the syntax of: echo("Hello…

Wow, I just have to reply! Which one of these do you prefer: echo("Hello") echo "Hello" "Hello".echo "Hello".echo() Or something different?

Yeah, it's truly is fascinating. Maybe

    echo "Hello"
Is the way ? :)

Re: Nim (formerly Nimrod) 0.10.2 released

#86

Post by wbhart »

daveroberts wrote: post #84
themartorana wrote: post #9

All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…

Go and Rust and included in the Computer Language Benchmark game: http://benchmarksgame.alioth.debian.org/ Nim, and many of the other interesting languages mentioned in this thread are not. I'm not sure if this is a cause or effect.

Not to mention, Nim still doesn't have a Wikipedia article because it is "not significant". http://en.wikipedia.org/wiki/Nim_(disambiguation)

Re: Nim (formerly Nimrod) 0.10.2 released

#87

Post by bluecalm »

andybak wrote: post #43
ebbv wrote: post #39

Earlier quoted context omitted.

Brief is not the same as lazy. I personally find comments that say what they mean to say in a short amount of text much more useful than ones that go on for paragraphs without saying anything new. I strive for brevity. I revised the one you responded to so you may want to check that now. As far as more details of what I don't like about Nim, that would have been easy to ask directly; I find the syntax of: echo("Hello…

> echo("Hello world!") I'm struggling to think how different it could be. Remove the parens? print instead of echo? It's a fairly minor point. I'm fairly very sensitive on issues of visual clutter in syntax and this doesn't bother me in the slightest. > I far prefer the set of cases to be indented from the case statement itself. As mentioned elsewhere this is optional but I do agree > And the "of" on each line is red…

The case thing appeared in some coding guidelines for difference languages (ex: https://www.kernel.org/doc/Documentation/CodingStyle). I guess experienced people who wrote a lot of code didn't like to waste indentation level. I do indent case's myself but I think not indenting them is not something to easily dismiss.

Re: Nim (formerly Nimrod) 0.10.2 released

#88

Post by [deleted] »

klibertp wrote: post #36
themartorana wrote: post #9

All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…

Actually it's being hyped that's weird. There are literally dozens of very interesting languages being created and developed right now and I bet you don't know of any of them. The only - and they are very few in comparison - languages which are being hyped since very early in their life cycle are the ones backed by corporations. Both Rust and Go are such languages and that's basically it. "Normal" languages live on a…

[deleted]

Re: Nim (formerly Nimrod) 0.10.2 released

#89

Post by audunw »

wbhart wrote: post #59
themartorana wrote: post #9

All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…

The main reasons I think, are that Nim is not "production ready" and that other developers think of Nim as Andreas Rumpf's baby. In my opinion, this happens when a single author is responsible for most of the implementation of a language. Another example of this is the Crack language, which is still essentially controlled by one person, despite people declaring it "ready for writing useful code". Two things make non-…

While Nim has mostly been developed by Andreas, there seems to be about 3-4 people working on the compiler and standard library. I've contributed a bit myself, and I've found Andreas and the other developers very friendly to outside contributions.

I am very optimisitic about the Nim community, it's still small but it is open and friendly, so I think all the potential for growth is there, especially now that the compiler itself is reaching maturity

Re: Nim (formerly Nimrod) 0.10.2 released

#90

Post by audunw »

wbhart wrote: post #59
themartorana wrote: post #9

All the hype on HN seems to be towards Rust and Go (with Go having its share of haters), but Nim sounds particularly interesting as a side-step from Python that runs faster than both Go and Rust. Can anyone give me some insight as to why it's not as hyped, if at all? I'm rather unfamiliar with Nim, and it's seems to have a smaller community, but it feels like it should be getting all sorts of love considering its spe…

The main reasons I think, are that Nim is not "production ready" and that other developers think of Nim as Andreas Rumpf's baby. In my opinion, this happens when a single author is responsible for most of the implementation of a language. Another example of this is the Crack language, which is still essentially controlled by one person, despite people declaring it "ready for writing useful code". Two things make non-…

While Nim has mostly been developed by Andreas, there seems to be about 3-4 people working on the compiler and standard library. I've contributed a bit myself, and I've found Andreas and the other developers very friendly to outside contributions.

I am very optimisitic about the Nim community, it's still small but it is open and friendly, so I think all the potential for growth is there, especially now that the compiler itself is reaching maturity

Post reply on HN