So /prog/, what do you think about current situation of concurrent programming?
Isn't it shit and pain in the ass?
Name:
Anonymous2011-12-19 0:37
I've been working on this problem for a while, and the general consensus is that it sucks. I'm implementing a language with autonomous mutex locking that goes through a governing lock controller, and implements simple keywords and operators for concurrency eg.
spawn (routine) //Routines are automatically concurrent loop- like functions
call (function) //Has the same effect as 'call' in some assembly implementations
statement { statement {statement }} //Where all would be distributed accross threads in the interpreter
I'll release the first version of the interpreter in a few months, but I can't promise anything; even threadsafeness will only come with maturation of the software, and I'm on the fence right now about implementing it in C++ or Erlang. Most likely I will implement it in Erlang due to C++ being utter malware where leaks are commonplace and Concurrency only comes in the form of shitty APIs (like pthreads) but I am new to Erlang, and that could ho,d me back, whereas I know C++ like the back of my hand.