<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>nindalf</author><text>There’s now 2 incentive to support ARM better - Apple’s move to ARM on the desktop and cheaper cloud bills if you’re willing to use ARM instances. Either one wouldn’t be enough of an incentive, but together it will cause a shift in the next 3-5 years.&lt;p&gt;Developers will become more aware of the differences between the architectures, tool chains will accommodate both better, people and software will stop assuming they are running on x86 as default. ARM won’t “win” the desktop or the server market, but it will become a viable alternative, squeezing the profits of companies who depend on x86.</text><parent_chain><item><author>RcouF1uZ4gsC</author><text>&amp;gt; The x86 processor was able to run the test successfully all 10,000 times, but the ARM processor failed on the 35th attempt.&lt;p&gt;I think this issue might prove a problem in the long tail of desktop and server software running on ARM.&lt;p&gt;A lot of desktop and server applications try to take advantage of all the cores. Many times, they are using libraries that were either implemented prior to C and C++ having defined memory models or else without that much care for memory model as long as it ran without issues on the developer computer (x86) and server (x86). Going to ARM is going to expose a lot of these bugs as developers recompile their code for ARM without making sure that their code actually adheres to the C&amp;#x2F;C++ memory models.</text></item></parent_chain></comment><story><title>Examining ARM vs. x86 Memory Models with Rust</title><url>https://www.nickwilcox.com/blog/arm_vs_x86_memory_model/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>vbezhenar</author><text>Smartphones used ARM for a while. I think that many of the major libraries were used in one or another project. So I think that this problem won&amp;#x27;t be as severe, because those bugs hopefully were fixed.&lt;p&gt;Also Raspberry Pi was a popular choice for many tinkerers for years which also helps with ARM penetration.</text><parent_chain><item><author>RcouF1uZ4gsC</author><text>&amp;gt; The x86 processor was able to run the test successfully all 10,000 times, but the ARM processor failed on the 35th attempt.&lt;p&gt;I think this issue might prove a problem in the long tail of desktop and server software running on ARM.&lt;p&gt;A lot of desktop and server applications try to take advantage of all the cores. Many times, they are using libraries that were either implemented prior to C and C++ having defined memory models or else without that much care for memory model as long as it ran without issues on the developer computer (x86) and server (x86). Going to ARM is going to expose a lot of these bugs as developers recompile their code for ARM without making sure that their code actually adheres to the C&amp;#x2F;C++ memory models.</text></item></parent_chain></comment><story><title>Examining ARM vs. x86 Memory Models with Rust</title><url>https://www.nickwilcox.com/blog/arm_vs_x86_memory_model/</url></story>