3 ms·
Of course a web server developer can think multicore is no big deal. The entire architecture of the web makes it easy to split load between entire machines, spl
by jerf 16y ago
Of course a web server developer can think multicore is no big deal. The entire architecture of the web makes it easy to split load between entire machines, splitting it automatically between two cores isn't that hard. And that's fine and dandy, as long as you're working in a domain where the real computational workload is being done somewhere else and you're mostly bashing <1MB of strings together. Pretty disingenuous to project out from there, though; ask the database implementors if anything has changed.
Also the conclusion is really weird; concurrency will be hidden away from programmers even more than it is now, but it will take the form of message passing and event-loop programming? That's hardly hidden, that's fundamentally rewriting how you write programs to work with concurrency. It seems to contradict his entire thesis. The details may be hidden but they already are; semaphores, for instance, are already an abstraction.