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?
[ Parent
| on HN ]
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.
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.
An interesting to reason to avoid GC would be a belief that you could make a usable general-purpose language without GC.
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.