7 ms·

After purchasing an M1, i'm starting to realize how viable ARM is as a main platform. Nearly everything I want to run on it has a natively built version, and r

by swalsh 5y ago

After purchasing an M1, i'm starting to realize how viable ARM is as a main platform. Nearly everything I want to run on it has a natively built version, and runs great on it. I could easily move anything I've built to a server running ARM with little frustration. I think that may be a bigger part of the coming future.

jes 5y ago
Same. I’ve been loving my M1 Mac Mini for almost a year. Cool, silent, fast and compact.
dippersauce 5y ago
Before M1 my only exposure to ARM has been low-power SBCs and Android devices, and the experience was mediocre in the “just works” department. Poor hardware support, and a lack of proprietary software support. Performance was also lacking. Apple’s tight integration and high-end CPUs have resulted in a vastly better experience, but I want to have more options than just macOS and MacBooks. I think we’re trending in the right direction, but it’s going to be a while before (5 years IMO) before we see anything approaching competitive to the M-series chips from major market players. If Microsoft could fix their frankly horrid x86 compatibility on aarch64 devices thing would speed along nicely I think.
- tenebrisalietum 5y ago
  > If Microsoft could fix their frankly horrid x86 compatibility on aarch64 device I don't think Microsoft is the real problem there, though. NT was developed to be portable and was working on architectures other than x86 in the beginning. So it was interesting when I heard things about "Windows on ARM" half a decade ago--and then the Surface RT. The RT was crap, but it did have real Windows NT working on non-Intel ARM, as was the OS on their Windows Series 10 phones or whatever. So Microsoft is already there on an OS level. It's the big software vendors that have to be corralled to switch somehow (Autodesk, Adobe, etc.) Honestly .NET overall was probably at least in part Microsoft trying to get developers on something more CPU-agnostic to reduce dependence on x86.
  - q-big 5y ago
    > I don't think Microsoft is the real problem there, though. > [...] > So it was interesting when I heard things about "Windows on ARM" half a decade ago--and then the Surface RT. The RT was crap, but it did have real Windows NT working on non-Intel ARM, as was the OS on their Windows Series 10 phones or whatever. In this specific case, Microsoft is the real problem: Microsoft deeply locked down the Surface RT; you needed a jailbreak to run unsigned applications on it.
  - atq2119 5y ago
    Parent's point was that Apple made the switch without having to get software vendors on the project, due to excellent emulation of x86 on their ARM.
    - webmobdev 5y ago
      Apple has more control over developers - these idiots pay them money for the "privilege" of developing on it. And Apple started by deprecating support for all 32 bits app. That forced many developers to refactor or port their code. The x86 emulation support will end in the near future and will force the remaining developers onto the ARM platform.
      - cs2733 5y ago
        Rosetta 1 was supported for 6 years. I don't think that's too bad.
  - codeflo 5y ago
    I'm not so optimistic. There are some technical things Microsoft did poorly when going from x86 to x86-64, which in my opinion delayed the transition of a lot of software by a decade. And this is with processors that can run both instruction sets natively, where no actual software emulation was required. To give some context (this started with Windows Server 2003 64-bit and is still how it works in Windows 11): Instead of implementing fat binaries like OS X did, they decided to run old x86 applications in a virtualized filesystem where they see different files in the same logical path. This results in double the DLL hell nightmare, with lots of confusing issues around which process sees which file where. For many usecases around plugins, this made a gradual transition impossible. (Case in point: The memory hungry Visual Studio is currently still 32-bit. Next release will hopefully finally make the switch.) Also, it’s surprising how much stuff in Windows depends on loading unknown DLLs into your process, like showing the printer dialog. So you run into these problems all the time. Have they learned their lesson? It doesn’t look like it. Last I checked, x86 on ARM uses the exact same system as x86 on x86-64. If they ever emulate x86-64 the same way, that’s triple DLL hell right there. And I don’t think they’ll get a decade to sort things out this time around.
- nightski 5y ago
  M1 is great but not everyone wants a SoC. I like the ability to swap out parts in my PC build.
  - webmobdev 5y ago
    And the freedom to run full featured alternative OSes on the bare machine.
  - m4rtink 5y ago
    All the M1 machines have built in RAM, right ? And GPU as well.
- mnadkvlb 5y ago
  I have tried buying microsoft arm computers since the last two gens now both the surface prox x with qualcomm sq1 and sq2 as well as another yoga book 5g. Windows performance on these platforms is so trash, you feel like going back ten years on ultrabooks. Even their own apps are not optimized or some like visual studio didnt even run. Compare that to x86 builtin emulation on apple m1, it performs so close to native performance on a 1000 bucks macbook air. Microsoft has definitely different priorities like how to chnange settings for a user without their permissions or how to hide settings so users have less choice. windows experience has been so downhill since win7.
  - freemint 5y ago
    Downhill compared to Win7, yes. Downhill ever since, no. Windows 8 was worse then 10.
    - mnadkvlb 5y ago
      i agree. But seems like microsoft is back to old habits in win11 with settings regarding browser settings etc. having different standards for edge vs others.hn discussion: https://news.ycombinator.com/item?id=28225043 https://news.ycombinator.com/item?id=28225043
  - dippersauce 5y ago
    I vaguely remember seeing a video demonstrating a an M1 device virtualizing Windows ARM faster than it ran on Surface ARM hardware. Kind of reminds me of how an Amiga of the era could be set up to virtualize(?) Mac OS faster than contemporary hardware Mac could.
  - dippersauce 5y ago
    It's tempting to blame the user hostility on corporate shortsightedness or disfunction, but I wonder if MS has a long-term plan here?
  - OneTimePetes 5y ago
    They want to be apple so bad, but they also want to be google so bad, not realizing that the overlapping set is empty. You cant be user friendly, private first luxury appliance and data-driven add sell-out at the same time. One dream has to die for the fish to fry.
lvl100 5y ago
Depending on the next iteration of Apple silicons, I am seriously considering a Mac Mini farm for compute heavy tasks.
- skohan 5y ago
  Would that really be a competitive option for your use case over something like graviton? It is kind of a wild state of affairs that as good a chip as M1 isn't available as commodity hardware.
ashtonkem 5y ago
I’ve been eyeing Graviton for our server work loads. On paper it’s price competitive.
- minimaul 5y ago
  We’ve been moving more and more to it. It works, and surprisingly well. It’s not quite up there for absolute single thread performance in our experience, but price/perf is excellent. edit: really, I’m just waiting for Graviton 2 Fargate support, and then I’ll be able to move a lot of workloads.
omegalulw 5y ago
I think we should look at one step further - RISC-V. Open source is the best way to ensure consumers don't get shafted by someone doing the Intel model again or Apple keeping M1 limited to their devices.
- skohan 5y ago
  Well I think it's clear that Apple will keep M1 to themselves. But I would imagine other vendors will come out with Arm offerings to compete. I agree a truly open-source option would be desirable.
- nicce 5y ago
  Open soure alone is not enough. Look at Chromium, controlled by a single company on what is decided
- mhh__ 5y ago
  You seem to be making the classic mistake of thinking that a given RISC-V processor is open source. The standard is open, the processor's source "code" (design) doesn't have to be. This does not mean RISC-V use wouldn't be a good thing, as it prevents a whole boatload of legal issues, but it just isn't what a lot of people seem to think it is. ARM could end up being a better ISA in the very high-clock high-IPC domain, it remains to be seen.
  - ksec 5y ago
    It is sad to see these sort of misinformation continue to spread like plague. Especially on HN.
  - omegalulw 5y ago
    I accept that I should have been more careful in my wording. I intended to comment that having an open source ISA that you could create processors for is a huge step in creating competition. If someone wants to compete with Intel they would have a hard time even if they make an excellent processor since they are unlikely to get a x86 license. With arm you have to pay licensing fee and control of the Isa is still with a private company. With risc v you can make your own processor and have a good shot in market. You will also have a chance to have a to propose/comment on future ISA changes.
sitkack 5y ago
M1 is the only arm part with memory ordering like x86. This allows them to hit x86 into Arm but not worry about the change in visibility to main memory by different threads. None of the server parts have that. But by the time you do run your code on an Arm server, most of the bugs will be worked out. The M1 is special.

by swalsh 5y ago

jes 5y ago

Same. I’ve been loving my M1 Mac Mini for almost a year. Cool, silent, fast and compact.

dippersauce 5y ago

Before M1 my only exposure to ARM has been low-power SBCs and Android devices, and the experience was mediocre in the “just works” department. Poor hardware support, and a lack of proprietary software support. Performance was also lacking. Apple’s tight integration and high-end CPUs have resulted in a vastly better experience, but I want to have more options than just macOS and MacBooks. I think we’re trending in the right direction, but it’s going to be a while before (5 years IMO) before we see anything approaching competitive to the M-series chips from major market players. If Microsoft could fix their frankly horrid x86 compatibility on aarch64 devices thing would speed along nicely I think.

tenebrisalietum 5y ago
> If Microsoft could fix their frankly horrid x86 compatibility on aarch64 device I don't think Microsoft is the real problem there, though. NT was developed to be portable and was working on architectures other than x86 in the beginning. So it was interesting when I heard things about "Windows on ARM" half a decade ago--and then the Surface RT. The RT was crap, but it did have real Windows NT working on non-Intel ARM, as was the OS on their Windows Series 10 phones or whatever. So Microsoft is already there on an OS level. It's the big software vendors that have to be corralled to switch somehow (Autodesk, Adobe, etc.) Honestly .NET overall was probably at least in part Microsoft trying to get developers on something more CPU-agnostic to reduce dependence on x86.
- q-big 5y ago
  > I don't think Microsoft is the real problem there, though. > [...] > So it was interesting when I heard things about "Windows on ARM" half a decade ago--and then the Surface RT. The RT was crap, but it did have real Windows NT working on non-Intel ARM, as was the OS on their Windows Series 10 phones or whatever. In this specific case, Microsoft is the real problem: Microsoft deeply locked down the Surface RT; you needed a jailbreak to run unsigned applications on it.
- atq2119 5y ago
  Parent's point was that Apple made the switch without having to get software vendors on the project, due to excellent emulation of x86 on their ARM.
  - webmobdev 5y ago
    Apple has more control over developers - these idiots pay them money for the "privilege" of developing on it. And Apple started by deprecating support for all 32 bits app. That forced many developers to refactor or port their code. The x86 emulation support will end in the near future and will force the remaining developers onto the ARM platform.
    - cs2733 5y ago
      Rosetta 1 was supported for 6 years. I don't think that's too bad.
- codeflo 5y ago
  I'm not so optimistic. There are some technical things Microsoft did poorly when going from x86 to x86-64, which in my opinion delayed the transition of a lot of software by a decade. And this is with processors that can run both instruction sets natively, where no actual software emulation was required. To give some context (this started with Windows Server 2003 64-bit and is still how it works in Windows 11): Instead of implementing fat binaries like OS X did, they decided to run old x86 applications in a virtualized filesystem where they see different files in the same logical path. This results in double the DLL hell nightmare, with lots of confusing issues around which process sees which file where. For many usecases around plugins, this made a gradual transition impossible. (Case in point: The memory hungry Visual Studio is currently still 32-bit. Next release will hopefully finally make the switch.) Also, it’s surprising how much stuff in Windows depends on loading unknown DLLs into your process, like showing the printer dialog. So you run into these problems all the time. Have they learned their lesson? It doesn’t look like it. Last I checked, x86 on ARM uses the exact same system as x86 on x86-64. If they ever emulate x86-64 the same way, that’s triple DLL hell right there. And I don’t think they’ll get a decade to sort things out this time around.
nightski 5y ago
M1 is great but not everyone wants a SoC. I like the ability to swap out parts in my PC build.
- webmobdev 5y ago
  And the freedom to run full featured alternative OSes on the bare machine.
- m4rtink 5y ago
  All the M1 machines have built in RAM, right ? And GPU as well.
mnadkvlb 5y ago
I have tried buying microsoft arm computers since the last two gens now both the surface prox x with qualcomm sq1 and sq2 as well as another yoga book 5g. Windows performance on these platforms is so trash, you feel like going back ten years on ultrabooks. Even their own apps are not optimized or some like visual studio didnt even run. Compare that to x86 builtin emulation on apple m1, it performs so close to native performance on a 1000 bucks macbook air. Microsoft has definitely different priorities like how to chnange settings for a user without their permissions or how to hide settings so users have less choice. windows experience has been so downhill since win7.
- freemint 5y ago
  Downhill compared to Win7, yes. Downhill ever since, no. Windows 8 was worse then 10.
  - mnadkvlb 5y ago
    i agree. But seems like microsoft is back to old habits in win11 with settings regarding browser settings etc. having different standards for edge vs others.hn discussion: https://news.ycombinator.com/item?id=28225043 https://news.ycombinator.com/item?id=28225043
- dippersauce 5y ago
  I vaguely remember seeing a video demonstrating a an M1 device virtualizing Windows ARM faster than it ran on Surface ARM hardware. Kind of reminds me of how an Amiga of the era could be set up to virtualize(?) Mac OS faster than contemporary hardware Mac could.
- dippersauce 5y ago
  It's tempting to blame the user hostility on corporate shortsightedness or disfunction, but I wonder if MS has a long-term plan here?
- OneTimePetes 5y ago
  They want to be apple so bad, but they also want to be google so bad, not realizing that the overlapping set is empty. You cant be user friendly, private first luxury appliance and data-driven add sell-out at the same time. One dream has to die for the fish to fry.

lvl100 5y ago

Depending on the next iteration of Apple silicons, I am seriously considering a Mac Mini farm for compute heavy tasks.

skohan 5y ago
Would that really be a competitive option for your use case over something like graviton? It is kind of a wild state of affairs that as good a chip as M1 isn't available as commodity hardware.

ashtonkem 5y ago

I’ve been eyeing Graviton for our server work loads. On paper it’s price competitive.

minimaul 5y ago
We’ve been moving more and more to it. It works, and surprisingly well. It’s not quite up there for absolute single thread performance in our experience, but price/perf is excellent. edit: really, I’m just waiting for Graviton 2 Fargate support, and then I’ll be able to move a lot of workloads.

omegalulw 5y ago

I think we should look at one step further - RISC-V. Open source is the best way to ensure consumers don't get shafted by someone doing the Intel model again or Apple keeping M1 limited to their devices.

skohan 5y ago
Well I think it's clear that Apple will keep M1 to themselves. But I would imagine other vendors will come out with Arm offerings to compete. I agree a truly open-source option would be desirable.
nicce 5y ago
Open soure alone is not enough. Look at Chromium, controlled by a single company on what is decided
mhh__ 5y ago
You seem to be making the classic mistake of thinking that a given RISC-V processor is open source. The standard is open, the processor's source "code" (design) doesn't have to be. This does not mean RISC-V use wouldn't be a good thing, as it prevents a whole boatload of legal issues, but it just isn't what a lot of people seem to think it is. ARM could end up being a better ISA in the very high-clock high-IPC domain, it remains to be seen.
- ksec 5y ago
  It is sad to see these sort of misinformation continue to spread like plague. Especially on HN.
- omegalulw 5y ago
  I accept that I should have been more careful in my wording. I intended to comment that having an open source ISA that you could create processors for is a huge step in creating competition. If someone wants to compete with Intel they would have a hard time even if they make an excellent processor since they are unlikely to get a x86 license. With arm you have to pay licensing fee and control of the Isa is still with a private company. With risc v you can make your own processor and have a good shot in market. You will also have a chance to have a to propose/comment on future ISA changes.

sitkack 5y ago

M1 is the only arm part with memory ordering like x86. This allows them to hit x86 into Arm but not worry about the change in visibility to main memory by different threads. None of the server parts have that. But by the time you do run your code on an Arm server, most of the bugs will be worked out. The M1 is special.