> Unfortunately, though Apple will likely find very great success with their ARM Macs, it does not necessarily follow that the architecture will gain significant ground outside the Apple-sphere.
Does not imply heavy workloads, compilation being offloaded to cloud is something already being done though.
I suspect that ARM will cannibalise most workloads, since it's shown very strong early competence already in photo and video editing on the iPad Pro, I highly suspect advancements in that direction will come to quallcomm CPU's in future.
ARM can eat the earth but it will not be a shift in a single year, I was suggesting a likely way forward and that is bottom up, coming from low end laptops to higher end laptops and eventually workstations and servers.
Just because it's not for -you- right now because you need local compilation does not mean a JS coder or a normal office worker would be unable to use an ARM based machine.
Nothing prohibits ARM from ever being workstation grade, it's just not the focus right now- but you seem to imply that because there's no workstation capable CPU that there never can be one, which I find disingenuous.
Just because it's not for -you- right now because you need local compilation does not mean a JS coder or a normal office worker would be unable to use an ARM based machine.
I don’t know what workflow other JS coders have, but mine starts with local development in Node. Does V8 produce code that’s as optimal for ARM as x86_64? That’s a pretty big deal to me, and can in fact be very enabling. The local development experience really needs to be good to build a platform, otherwise development will be halting and piecemeal the way embedded development usually is.
> never tested on android
just as planned
???
I’m back-end, not front-end. I think I mentioned Node, right? Why would I test backend code on a phone?