A programming language does not need to include anything new to be a better language, it is enough to offer a combination of good features that do not exist together in competing languages.
"Parallel threads of execution that explicitly listen for and send messages" as the authors says, already existed in Ada (1979).
Moreover, such concurrent programming already existed in PL/I, in 1965. PL/I, in 1965, was actually much more convenient than the supposedly modern POSIX pthreads, because it was the first to include the equivalent of WaitForMultipleEvents, which is sorely lacking in POSIX.
The languages available on cheap computers, e.g. BASIC, Pascal or C, had less features, especially features for parallel processing, which were not useful on cheap hardware.
In time, the cheap computers became more powerful than the old supercomputers. Then many of the features formerly available only on powerful computers were added to the new popular programming languages, but not all of them.
While what were considered large languages during the sixties, e.g. PL/I and ALGOL 68, had a few serious flaws, they also had many nice features that are still not present in the most popular programming languages of today, mostly as a consequence of the fact that while C has taken most of the features it added over BCPL and B from either PL/I or ALGOL 68, it simplified those features a lot or even crippled them compared to the original, in order to allow implementation on much cheaper computers.
Later languages attempted to be better than Pascal or C, which was a very easy target, but their designers did not study what was available in earlier languages, to be also better than that.
At least to me, "The seven ..." reads as the author saying "there are exactly seven of them, and they are these: ..."
> A lot of work was done on how to make Smalltalk run fast and efficiently, culminating in the Strongtalk project. Strongtalk is historically important because its discoveries became the basis of the HotSpot just-in-time compiler for Java.
It's also the basis for v8! Truly an important project.
> Second, Erlang switched the notion of a thread of execution jumping from object to object to run various code and instead had parallel threads of execution that explicitly listen for and send messages.
I'm glad I'm not the only one that noticed the similarities between OO in the Alan Kay sense and Erlang. An extension of that would be the microservice architecture of today. You have encaspulation, late binding, and message passing.