Ben, this is a thought-provoking comment! In my opinion, making everything easy(/hard?) by not relating to or hiding concurrency, or even refuse that concurrency is needed at the conceptual level (“all we need is callbacks and an event loop”), is throwing the baby out with the bathwater.
You are of course right about Turing: basically every paradigm can implement anything. Since this thread arose my attention 168 days after the previous comment because it had “concurrency” in the title, then that’s what I wonder about. How does the Meteor framework handle concurrency? At a possibly lower level? Or will you need opsys help? Or will react.js satisfy all the (quasi/real)-concurrency you need? By the way, concurrency always is quasi (there is a scheduler somewhere), but parallelism is true multi-core. Or are there any other obvious ways? Or is it a no-case, not in scope for the applications you’re building? The latter would seem rather strange (and interesting) to me.
I have tried to raise the question again in a new note (here). I am excited to learn what this community’s answers are.