Bingo, generalized statements like this help no one. It’s a very narrow-minded view of software engineering. Instead the author should adopt a more pragmatic view of the world of coding. We don’t live in a black and white world and software is no exception. Use the right tool for the job and remember everything has tradeoffs.
"generalized statements like this help no one."
May I cite this when I explain recursion?
SCNR
My answer to almost every tech choice question these days is "it depends". I think as you mature as a developer you see the trade offs with everything.
shouldilistentothiswebsite.com is available (for now)
Besides, I think the author is missing the point. Sharing memory between threads is a huge part of what makes them fast. The difficulty doesn't lie in having to deal with mutexes - in fact I think mutexes and critical paths are easier to work with than message passing. Instead, the difficulty lies in trying to weave all these parallel moving parts together in a way that's both fast and correct. Synchronization primitives are easy, it's the actual synchronization that's hard, and multi-process doesn't fix that.