Earlier quoted context omitted.
Smartphones are a good argument for both views IMHO. Native development (as in native machine code executables) on Android is still a terrible experience even though they had a decade to fix it. It's much better on Apple platforms, maybe because they actually cared about developer-experience and native code is a "first class citizen" there. It goes beyond the different instruction set of course and most of the time t…
What do you think can be improved in Android? Unlike iOS, Android is actually running in diverse hardware. All iOS devices are Arm, where as Android will run on x86. That alone makes it more of a hassle.
Linus Torvalds on Why ARM Won't Win the Server Space
331–340 of 545 posts
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#332Re: Linus Torvalds on Why ARM Won't Win the Server Space
#333I am fine with x86 being successful - there are good reasons for it. I don't get why there's this ARM push in the PC and servers market. It's not making anything better.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#334Earlier quoted context omitted.
Well nobody uses NetBSD so... Sure portability increases code quality, but at what cost to time to market which seems to be the primary concern for most developers these days?
NetBSD (and NetBSD code) is used pretty much everywhere. The internet pretty much runs on it.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#335Earlier quoted context omitted.
Node and Ruby applications do fail on ARM though, when it comes to native libraries and extensions. And now your whole distro is different than your development machine, which adds complexity. Do I really want to be debugging why node-gyp fails to compile scrypt on the ARM distro on the new Amazon A1 ARM instance (which it did in my case)? And if I solve that, what about the other 2451 dependencies? Let's pessimistic…
I'm suffering through this now -- I have a custom C++ Node exception that needs to run on both x64 and ARM. The ARM cpu is onboard a mobile robot, where I care about power draw. The good news is that Clang can cross-compile fairly easily. Much better than gcc. The bad news is that there are a surprising number of missing libraries on Ubuntu/ARM64. For example, Eigen3. And although the code is fairly compatible, there…
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#336Re: Linus Torvalds on Why ARM Won't Win the Server Space
#337Earlier quoted context omitted.
When Apple replace Intel with ARM in their laptops, that goes away too. (See my argument elsewhere in this thread)
Apple is a small percentage of the laptop market.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#338Earlier quoted context omitted.
> I think I'll side with Linus on this one. I saw first-hand how non-existent the x86 Android market was, despite Intel pouring megabucks into the project. Doesn't that refute Linus' argument, not strengthen it? Almost all Android developers develop on x86. Intel thought, as Linus apparently does, that this would drive adoption of x86 on phones. It didn't. Intel even got competitive in power efficiency and it wasn't…
Phones are different than servers though. The primary customer of a phone is Joe Somebody who doesn't know or care about architectures, only battery life and cost. Well ARM wins there. The primary customer of servers is developers who care less about cost and more about time to market.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#339Earlier quoted context omitted.
On a related note, if Apple does switch to ARM chips for their laptops, that will make mainstream ARM server-side development more viable than any cross-platform story ever can. Or kill the Mac desktop. One or the other :)
I don’t think that it would kill desktop, but I’m sure that unless ARM will be much faster, developers will use x86 macs for a long time.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#340Earlier quoted context omitted.
> When developing for iOS you typically interact with the iOS simulator on your desktop, which natively compiles your app against x86 versions of the mobile frameworks. And the fact that the "develop on x86, test on ARM" workflow works so smoothly on iOS is strong evidence that Linus is wrong.
Who's going to make the "develop on x86, deploy on server-side ARM" experience smooth? It certainly isn't today. Who has that kind of control of the entire stack top to bottom? Amazon is the only one that comes to mind... but I wouldn't bet on it.