4 ms·
It was painful - mostly because we don't have good tools for that sort of thing and most of our programming sort of hides the idea of multiple CPUs and pretends
by abritinthebay 9y ago
It was painful - mostly because we don't have good tools for that sort of thing and most of our programming sort of hides the idea of multiple CPUs and pretends it's all working at once (in terms of us writing the code anyhow).
It's all abstracted in a very linear way.
Changing all that will take a lot of time if we do.
- gpderetta 9y agoActually multiple CPUs are not normally hidden in mainstream programming languages [1]: i.e. threads are visible. The fiction that it is maintained by the programming languages and hardware is that of a single, coherent address space, which Cell very much did not have. [1] outside of parallel iteration/folding constructs.
- abecedarius 9y agoYeah. Erlang seems to show that there is a path from here to there, but the Erlang-ish world is tiny relative to the whole industry.