There are libraries, frameworks, languages and runtime environments that seek to shield software developers from having to understand concurrency–or at least are said to do so. In my experience, this doesn’t work.
I’m all for making developers’ lives easier and sparing users the effects of concurrency-related implementation errors. But tool support gets us only so far: we might succeed in making concurrency-related concerns invisible to developers, but they still need to understand concurrency issues on a conceptual level–maybe doubly so if they’re invisible in code. Failing that, we likely end up with beautifully looking code that blows up in amazing ways at runtime.
Been there, done that, yet another t-shirt is being printed as we speak.