Writing code because of the details of how some processor does something isn&#x27;t modernization; it&#x27;s 1965-ization. (Which is not to say that optimization doesn&#x27;t take place in a modern contexts: of course you need a fast video codec on your mobile device or whatever; it&#x27;s just not in an of itself modern).<p>I&#x27;m not going to wreck my programs because of what Intel (of all companies) thinks.<p>The problem here is that although the chip designers care about how people program at a higher level above the instruction set, and design the hardware accordingly, their scope of what that means is limited to the C language. (For instance, here, this is what Intel are referring to when they say they have a line up of compilers, libraries and debuggers for you.)<p>Sorry, Intel: &quot;write your code in C (in a &#x27;cache-friendly&#x27; way: no linked data structures), with a smattering of such and such libraries for parallelizing it&quot; is not &quot;modernization&quot;.