Am 13.11.2010 08:53, schrieb Russel Winder:
On Fri, 2010-11-12 at 15:07 -0500, Jeff Nowakowski wrote:
[ . . . ]
The lack of generics and dangerous concurrency are much bigger issues.
If D can actually be shown to be a useful concurrent language, instead
of the buggy and incomplete mess it is now, then it might have something
to crow about.
What do you see as wrong with the Go model for concurrency?
I find the process/message-passing approach infinitely easier than
shared-memory multithreading with all its needs for locks, monitors,
semaphores or lock-free programming. True operating systems will need
these latter techniques, but surely they are operating system level ones
and should never have to appear in application code?
...True operating systems will need these latter techniques...
gain speed and very granular control by introducing more risky technics:
that not only a need for True operating systems, Ds approach is to allow
(i hope better/less risky) both
