Here's something to offset all the
long discussions on typing that
have been taking place recently
(see Concurrent Components With Message Passing):
In our experience, the right default for structuring programs is as concurrent components that communicate through asynchronous message passing. Components should be sequential or communicate synchronously only if necessary. This is not a new idea; Carl Hewitt anticipated it thirty years ago in the Actor model. But today we have many strong reasons for accepting it. For example: [...] (discussion continues with
references to Erlang, E, and CTM)
[...] Unfortunately, these reasons and their conclusion are almost completely ignored by mainstream languages and by books on program design. In both, object-oriented programming and shared-state concurrency are given priority, even though they are the wrong default. [...]
So, is this heresy or an unfortunately ignored truth?
Recent comments
14 weeks 7 hours ago
18 weeks 2 days ago
19 weeks 6 days ago
19 weeks 6 days ago
22 weeks 4 days ago
27 weeks 1 day ago
27 weeks 1 day ago
27 weeks 4 days ago
27 weeks 4 days ago
30 weeks 3 days ago