News for hackers. Stuff that matters.
Re:On Rust and Nim by aphexairlines on Sunday February 22, 2015 @06:18AM (#9089040)
Looks like comparing apples and oranges. If Nim has a GC it would be more instructive to compare it with another garbage-collected systems language like OCaml.
Re:On Rust and Nim by andreaferretti on Sunday February 22, 2015 @11:15AM (#9089808)
Yes and no. In fact, Nim can be used without a GC. Actually the GC of Nim is written in Nim, which certinaly proves the point. Now, it is not really convenient to avoid the GC in Nim, and you certainly do not have the safety features of Rust, but it can be done when needed (and you are still writing in something more productive than C)
Re:On Rust and Nim by z92 on Sunday February 22, 2015 @06:58AM (#9089094)
What's wrong with comparing a GC language with non-GC language?
Re:On Rust and Nim by lifthrasiir on Sunday February 22, 2015 @07:16AM (#9089130)
Wildly different goals, given that there should be some interesting reason to avoid GC nowadays.
Re:On Rust and Nim by rdtsc on Sunday February 22, 2015 @11:56AM (#9089955)
How are they "wildly" different. I can see different but "whildly" really?

GC is an implementation detail with some performance characteristics. Nim can turn its GC off. It can do a soft-realtime GC behavior where you limit its maximum time slice.

Re:On Rust and Nim by tomjakubowski on Sunday February 22, 2015 @02:01PM (#9090516)
> Nim can turn its GC off.

At the expense of losing memory safety.

Re:On Rust and Nim by twic on Sunday February 22, 2015 @08:47AM (#9089378)
An interesting to reason to avoid GC would be a belief that you could make a usable general-purpose language without GC.
Re:On Rust and Nim by Ygg2 on Sunday February 22, 2015 @08:57AM (#9089414)
Or having code that's callable from another GC-ed language like Ruby/Python/etc. Two GCs dancing around each other (e.g. Python calling Nim) is a recipe ripe for problems.
Re:On Rust and Nim by moomin on Sunday February 22, 2015 @08:53AM (#9089398)
Mostly that we already know what the answer's going to be.