Quote:
Originally Posted by chucker
Well, it’s still much harder to write code that takes good advantage of multiple cores, thanks in part due to the widespread imperative approach.
|
^--- this.
Getting back to your comment re: "IOW, it barely does" I disagree. Swift's computation model under the hood was designed for multi-core expression (not programming, expression post-compilation), LLVM was designed for runtime linking *and optimization* of computational units based on existing hardware availability, Apple Silicon is an ARM derived design that is geared for flexible shuttling of instructions and data on demand, etc, etc, etc. VE HAFF VAYZ.
This has literally been brewing for 20 years, but held back by the need to rely on Intel. Now that is dropping off rapidly, it'll be highly interesting to see what comes to fruition. Nobody right now has the groundwork laid like Apple.
PB, nobody should have to write for multiple cores, ever. The vast majority of such situations are well known, automatically detectable, and can be handled at compile time cleanly *if* the target architecture allows for clear and simple translation. That it must be currently architected and implemented that way by hand is a failure of the single core design dominance holding back the industry.
CISC winning out over RISC was a tragic misstep.