Original link: How Multicore CPUs Killed Object-Oriented Programming / Dev.
I think the answer is NO.
As I wrote on LinkedIn:
I think the article is missing a few points.
1) It is true that some newer languages like Go, Rust and Zig avoid classic OO concepts - but other newer languages like Kotlin, Swift and Ballerina have them. So not a total change of direction. I see it as that low level languages competing with C do not see the need for classic OO while languages intended for business applications do see the need for classic OO.
2) Before computers with single CPU with multiple cores we had computers with multiple CPU's with single core. The big change was when OS back in the early 90's started to support scheduling on multiple CPU's. The invention of multi-core just made it available at a PC price point.
3) Single core is actually no guarantee against concurrency issues in multithreaded programming. In general the OS scheduler may preempt a thread in the middle of something and let another thread run. The switch from single core to multi core did not change any multithreaded applications from correct to incorrect. Correct applications was guaranteed to work properly before and after. Incorrect applications could fail to work properly before and after. The switch just increased the likelihood of actual problems by several orders of magnitude.