It was pioneering in how low-cost and mass market it was at launch, but before the Pi there was plug computing, largely based around Marvell Kirkwood processors. There were also a variety of hackable NAS devices, I used some with Orion5x CPUS in. Then before plug computing there was the linksys NSLU2 with its Intel Xscale IXP chip, and all the hackable linksys routers going back to 2002, and that's just some of the stuff I've played with over the years. Before that I imagine there were previous generations of linux ARM support.
The Pi and other hobby boards are really great, don't get me wrong, but there's a tendency to credit them with a bit too much.
For their time (20 years ago), they certainly were cheap. $100 or so for a small power efficient box that could run almost a whole Linux distribution was an amazing bargain. Before that, you needed a good-sized desktop or server to do anything involving a Unix-like OS, or paid dearly for the convenience of a laptop.
And it wasn't much before that, that running Unix on any microcomputer was just a dream.
It's hard to comprend just how amazingly affordable computing has become in such a short amount of time.
I remember that time in my life very well. I literally had around $50 in my local currency in the coin box, and that was it. Hand me down computers were unavailable where I was.
Yes, it reached a wide audience, they did a lot of great stuff getting capable dev boards out to a lot of people. But fully functional Linux on ARM pre-dates the Pi significantly.
(I’d argue the NSLU2 and sheevaplug were both pretty affordable, at sub-$100 too, but the Pi definitely upped the game there)
It is my contention that this support was largely already present. That's all.
Pi did great work getting cheap boards out to people, and put a lot of effort into education and community building. They exposed a huge number of people to the possibilities of non-x86 computing that otherwise might not have been. So indeed let's credit them with that, it's all great stuff!
But it's quite revisionist to say they helped get linux or BSD or their tools onto the platform, IMHO.
If Pi3 was so popular, why didn't it exist as a binary?
Beyond that, I can only hypothesize that Docker on non-x86_64 (or multiarch Docker, in general), was very difficult to kick-start for whatever reason. This may have been compounded by the fact that Docker wasn't as broadly adopted by hobbyists back then, so demand for ARM builds want that great.
Getting more attention to the platform was definitely a good thing, exposing more people to a different architecture, to having a machine cheap enough to just play with, to all sorts of great stuff.
But Linux and BSD themselves were already mature on arm by that point.
Whoa, haven't heard that one in a looong time. Still have mine sitting in a storage closet, I think...
I used to run my own mail server on one and use another as a media server. I even did a small hardware mod and soldered a wifi card to one of the internal USB headers on one of them. Much fun!
I don't imagine the processing power stands up to modern devices though :)
Pi entered a mature ecosystem, it just made it a bit more consumer/newbie facing but the system level foundations were all there.
Ironically the Pi isn’t even particularly well supported in terms of drivers compared to commercial offerings.
While strongarm and others have been around longer, none had any real mass market hold. With Pi & co, you can build a (slow) server with $35. You can build a k8 cluster with $150. That's why we have cross platform packages for almost anything server related.
Fast forward to today, you can apt-get cross-compilers and build tools.
M1 probably enables the same transition for customer-oriented, proprietary apps. But it has little to do with cloud computing, except proving that performance and ARM are not mutually exclusive, thus providing more acceptance.
Well, to be honest it was probably macos+M1 platform support. Docker runs a virtual machine with Linux in it on macos and windows, not sure improvements there directly translate to server workloads. I am not sure about node, but it was surely working very well on ARM before that, although it might gain some optimizations thanks to M1.
If there are CLI ways to do this stuff I'd love to hear them.
I know sshd is controlled through systemsetup[1].
sudo systemsetup -setremotelogin on
None of the paid software with a tiny userbase you're thinking of is relevant to the server market, the point is that it's free and open.
I don't disagree, but going mainstream is different.
>It’s not apple M1 that’s making this migration possible, its just the cherry on top of a cake.
M1 would not exist without the Apple's App store all based on ARM.
Apples are upset their $2000+ laptop isn't the revolutionary catalyst for the Arm revolution but instead a crappy $25 computer that's been around for a decade.
Raspberry Pi, BeagleBone and various arm based embedded systems played a much higher role in getting most linux, BSD tools working under arm.
Same thing that’s happening now with RISC-V and SiFive’s boards.
It’s not apple M1 that’s making this migration possible, its just the cherry on top of a cake.
The cake was all those consumer arm boards and dev kits which got in the hands of various OS developers, software maintainers. Who put in their time to port their codebases to arm and ensure compatibility.