3 ms·

I think not having a parallelism first mindset will be the killer of the language. It's too important in today's world to not have that be an essential part of

I think not having a parallelism first mindset will be the killer of the language. It's too important in today's world to not have that be an essential part of the language from the beginning. Rust and go for example we're 100% designed around parallelism.

RX14 8y ago
I think you're getting confused by concurrency and parallelism. Crystal is concurrency-first and uses the same concurrency model as go. Expanding that to run fibers on multiple cores is just an implementation detail. A difficult implementation detail, but it shouldn't affect the core of the language.
- geezerjay 8y ago
  You posted a message that's essentially hand-waving. Discussing semantics means nothing if the language supports neither parallelism nor concurrency.
  - RX14 8y ago
    But crystal support concurrency, and it supports it very well. That's why it achieves about 100,000 HTTP requests per second per core, you just can't get that kind of performance on a single core without using evented IO.
coldtea 8y ago
>I think not having a parallelism first mindset will be the killer of the language. "Parallelism first"? That's a contentless statement that borders on marketing speak...