3 ms·
Seems like Go would be a good fit here - true parallelism would have to handy since I'd imagine you'd often want to have several control routines running at onc
by TylerE 12y ago
Seems like Go would be a good fit here - true parallelism would have to handy since I'd imagine you'd often want to have several control routines running at once.
- hardwaresofton 12y agoIt is, which is why the same people also do: http://gobot.io/ http://gobot.io/ I agree, I don't know if Ruby is the greatest choice for a language so close to low-level. But, I am glad it (artoo) exists
- vidarh 12y ago"True parallelism" is not a problem in Ruby at all. If you stick to threads, then there is the global interpreter lock, yes, but that has much less impact than people tend to think unless you depend on lots of poorly written C extensions. Especially on small systems without lots of cores. And you don't need to stick to threads.
- TylerE 12y ago"True parallelism" is EXACTLY not having a GIL.
- vidarh 12y agoIt appears you missed the last line of my comment: And you don't need to stick to threads. Anyway, the GIL makes no difference to the level of parallelism of most Ruby apps unless you're on a server with lots of cores, so all you're really saying is that "true parallelism" is irrelevant for most use cases. On a server with lots of cores, it can start becoming a constraint if you can't use multiple processes for some reason, but if you become constrained with it on the type of small systems this is intended for you're doing something very wrong.