It's of course impossible not to respect Linus' opinion and first hand experience in this space, but doesn't this whole post completely ignore the 100 ton blue whale in the room? Namely smartphones . That's an entire enormous segment of the industry and it's nearly 100% (or entirely 100%?) literally develop-on-x86-deploy-on-ARM. Smartphones also fit > "This isn't rocket science. This isn't some made up story. This is…
He did address the so-called 100-ton blue whale at the end: > End result: cross-development is mainly done for platforms that are so weak as to make it pointless to develop on them. Nobody does native development in the embedded space. But whenever the target is powerful enough to support native development, there's a huge pressure to do it that way, because the cross-development model is so relatively painful.
Linus Torvalds on Why ARM Won't Win the Server Space
161–170 of 545 posts
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#162Except that doesn't quite explain why soo many developers use macbooks (OS/X), yet deploy on Linux. Personally I think ARM could be leapfrogged by RISC-V, though it will take longer than people predict.
1. OS/X is Unix[tm] and linux is a "Unix clone" so the operating system works the same and (for purposes of this debate) both run on the X86 ISA.
2. The first thing all the macbook developers do is install Homebrew or equivalent and install all the same packages that are installed in their linux deployment environment.
At that point, their OS/X development environment is effectively indistinguishable from their linux deployment environment.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#163He refused to switch to gpl3 back in the day because 'it would be impossible to contact all contributors and get their permission' but last year he suddenly didn't need the same.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#164It matches my mindset. I am also looking for the good arm laptop. I do not need anything fancy: 4GB of ram (or better), 64GB SSD, wifi, bluetooth, usb (3 if possible), audio jack, good screen, usable keyboard, good touchpad.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#165It's extremely hard to agree with Linus on that. One problem in his argument is that he believes that everybody has a kernel hacker mindset: most today's developers don't care about environment reproducibility at architecture level. The second problem is that he believes that every kind of development is as platform sensitive as kernel hacking, and he even makes the example of Perl scripts. The reality is that one ye…
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#166Re: Linus Torvalds on Why ARM Won't Win the Server Space
#167Earlier quoted context omitted.
And he's wrong. In the enterprise, the vast majority of devs are on Windows, for Java for example. That doesn't mean that their deployment target is Windows, most of the time it's Linux. And the development differences, chance of bugs, performance profiles are way different between OSes than they are between CPU architectures.
> That doesn't mean that their deployment target is Windows, most of the time it's Linux. I don't feel like that's true. I don't have data to say otherwise, but my impression for the majority of non-tech businesses I encounter is that they are very much still Windows shops, and still on-prem.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#168Earlier quoted context omitted.
I do buy Linus' argument, you need to be able to do native development. My ARM64 development machine is a Pinebook, ARM32 a Cubietruck. Both have only 2GB of RAM and could really do with more. At least the Cubietruck has SATA so mine has a SSD.
With rich language runtimes, as app developer I don't care if my application instance runs on top of an OS, hypervisor or just plain bare metal. The only devs that need to care about the native part are the ones writing the glue between runtime and hardware.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#169It's of course impossible not to respect Linus' opinion and first hand experience in this space, but doesn't this whole post completely ignore the 100 ton blue whale in the room? Namely smartphones . That's an entire enormous segment of the industry and it's nearly 100% (or entirely 100%?) literally develop-on-x86-deploy-on-ARM. Smartphones also fit > "This isn't rocket science. This isn't some made up story. This is…
Linus is mostly wrong except for HPC. Very few dev pipelines for folks result in native executables. The vast majority of code is delivered as either source (python, ruby, etc) or bytcode, JVM, Scalia, etc. And the Xeon class machines folks deploy to in data center envs is a world apart from their MacBooks. These truths are true for Linus, but not for the majority of devs. Even those creating native binaries, this is…
This wasn't showstopping by any means, but it did take a couple of hours to tweak it until it ran properly, and this was just a small webapp not really doing anything exceptional.
Our main line-of-business app (on Java) runs on SPARC/Solaris in production, so we have on-premises test servers so we can test this... and yes, there have been quite a few instances where we identified significant performance anomalies between developer machines running x86/Windows and our Sparc/Solaris test environment, and had to go rewrite some troublesome functions.
Re: Linus Torvalds on Why ARM Won't Win the Server Space
#170Earlier quoted context omitted.
> Mobiles are mostly communication Communication is also work, especially as you go up the management value chain. I think maybe people should refer to the thing that PCs do and mobiles don't as "typing".
It’s definitely a different kind of work. In general, smartphone software is built to discourage creative work and focus on either reading or communicating.