Is ARM Ever Coming To the Desktop?

First time accepted submitter bingbangboom writes "Where are the ARM powered desktops? I finally see some desktop models however they are relegated to "developer" models with USD200+ price tags (trimslice, etc). Raspberry Pi seems to be the only thing that will be priced correctly, have the right amount of features, and may actually be released. Is the software side holding ARM desktops back? Everyone seems to be foaming at the mouth about anything with a touch interface, even on the Linux side. Or are manufacturers not wanting to bring the 'netbook effect' to their desktop sales? Are ARM powered desktops destined to join the mythical smartbook?"

Comments

Re:Why?

[Bert64]

Exactly, no solution fits all... Your needs are specialised, so you will occupy a niche of people who will continue to buy highend workstations...

For the vast majority of people computers became powerful enough for their requirements many years ago (aside from increasingly bloated software trying to mask that fact), and they are concerned about price, running cost (ie power usage), noise and that the machine is not an eyesore, and even more so are the companies who buy hundreds of desktops for their employees and don't want to buy a noisy, expensive, large and power hungry workstation for someone who's sole business use for it is to write letters.

Re:Tabtop momentum building

[hairyfeet]

I'm sorry but.....why? WTF would you want ARM on the desktop? Are you living in a mud hut in Zambundi and don't have any electricity to spare for a desktop?

Lets be honest folks, the big selling point of ARM is how cheap it is on batteries. Well guess what you do NOT need when you are inside? Why that would be a battery! See that plug on the wall right in front of you?

Cycle for cycle x86 stomps the living shit out of ARM, it just uses more power to do so than most mobiles can afford due to the fact we haven't had a real breakthrough in battery tech in ages. Well that and the fashionistas at Apple have made iSliver batteries the "in" thing in which means you have to power the thing on a battery the width of a tic tac. I don't care if you put 8 cores on the thing, a bottom o' the line AMD quad, even the low power AMD quads, will stomp the living shit out of ARM. drop in an i series and it isn't even funny how badly it gets stomped.

Like everything else it is about using the right tool for the job. ARM royally kicks ass in mobile, embedded, and in places where you need a device that'll take milspec levels of abuse due to the fact you can run it fanless. X86 kicks ass in desktop and laptop where you want more performance and don't mind giving up some battery life for it. But ARM on the desktop makes about as much sense as stuffing an i series into your phone, that is none at all. The majority of code out there is x86, even on Linux x86 outnumbers ARM code by a pretty wide margin. So unless you just really really REALLY want the Droid version of Angry birds on your desktop it just seems more than a little stupid to be running a mobile chip in a place where you are right beside a plug in.

Re:Look on eBay

[mountaineer76]

Totally agree, just compare RISC OS 2 or 3.1 to the equivalent Windows version in 1988 or so, Acorn was streets ahead. Still have a 200 mhz RISC PC sitting next to my desk, it's a nippy little beast boots in a few secs or so....

Re:Tabtop momentum building

[jd142]

I'm sorry but.....why? WTF would you want ARM on the desktop? Are you living in a mud hut in Zambundi and don't have any electricity to spare for a desktop?

Lets be honest folks, the big selling point of ARM is how cheap it is on batteries. Well guess what you do NOT need when you are inside? Why that would be a battery! See that plug on the wall right in front of you?

You know, it's just possible some people might want to conserve electricity. Or even shave a couple of bucks off the old electricity bill. Just because you can use a resource, doesn't mean you should. I have running water, but I don't just leave the faucet on all day in case I might want a glass of water.

I don't know, but if you had one of those little portable solar cells, could you just power an arm laptop anywhere?

Re:Tabtop momentum building

[m50d]

ARM is admittedly easier than many things - you're still 32-bit and usually don't have endianess issues. So the main problems are sizes/alignment of system data structures - things like (network) host information, or even something as simple as date/time vary. Of course you should be using the types opaquely, but it's very easy to accidentally stuff a time_t into an int, and even if you are being careful you can miss implicit assumptions you're making (one of the problems I saw was code not dealing with an array in the network host data structure being of length 0). In this particular case the biggest source of problems was multibyte character handling differences (it was a Japanese game). When porting old code away from x86 you can also get a whole slew of floating-point related bugs, because double on x86 is really x87 extended double (I only encountered one minor problem in this case, it didn't do much floating point, but for other software it would be a bigger issue). Also see the recent glibc memcpy vs memmove issues for something that can come up even on x86-64 vs x86-64.

Once code's been ported to two or three architectures these problems don't tend to come up any more (because the first couple of changes reveal all your implicit assumptions that could be broken), and that's true of a lot of open source projects. But any code that's only ever run on one platform will have portability issues. You don't have to take my word for it - try it yourself, pick a random project that doesn't release non-x86 builds off sourceforge and try and build it for arm.