-
Notifications
You must be signed in to change notification settings - Fork 2
Deeply sequential nature of software must be replaced
In modern software, we must avoid sequential programming as much as we can. Sequential algorithms were widely developed decades ago, but now we see a rise of multi-core processors in nodes formes large distributed computing networks. So there are huge efforts done on software parallelization still having programming habits of sequential programming leads to a software paralyzation.
There are two widely known approaches to represent natively parallel software systems:
- DataFlow structures, can itself be based at a lower level on
- (async) message passing and the actor object model.
Message passing and actors were available still the 70s in production-ready Smalltalk systems. It is fun to see how large hype screams about appearing features and libraries in every next Java release or other mainline programming languages, while it is still stealing implementation of some like features available in old tubby Smalltalk decades ago.