Idea for Threading/concurrency API about citrine HOT 5 CLOSED

I have to think about this, so much possibilities, your suggestion looks promising though...

from citrine.

I much prefer the event-driven model, as used in Node.js, to threads, which I feel are hard to understand (mutex locks. etc.).

from citrine.

what do you think about async etc? could we facilitate that as a message, somewhat like 'catch'?

from citrine.

There's a problem.

In a dynamically scoped language with concurrency/parallelism the behavior of your program depends on the behavior of the scheduler, which is generally not visible to the programmer. In fact, if the scheduler is nondeterministic, your program may be nondeterministic. Fun!

So why is Citrine dynamically scoped?

see also http://clojure.org/index

from citrine.

Dynamic scoping was easier to implement and I want to find a reason to upgrade to lexical scoping. However dynamic scoping offers a lot of benefits, it solves a lot of problems in dynamic OOP languages regarding dependency injection, service location, globals and wiring.

I'm not afraid of concurrency in Citrine, we already solved a lot of issues that seemed ugly at first but turned out to be trivial. I see concurrency as a challenge but also as a possibility to explore how parallellism may work together with dynamic scoping rules. Non-determinism is not really an option though. Well see what happens, it's fun!

from citrine.