5 ms·

Are you going to run Apple software on your servers? Most servers leverage the Linux ecosystem, most of which is open-source and maintained by developers who do

Are you going to run Apple software on your servers? Most servers leverage the Linux ecosystem, most of which is open-source and maintained by developers who do not have big $$$. 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.

thecompilr 5y ago
Huh? I am developing natively in macOS for a Linux server using Rust. Everything just runs fine on both. Unless I need to go really low into syscalls I have no reason to be writing and testing my code on Linux.
- the_mitsuhiko 5y ago
  You’re supporting that point though. A big initial move for ARM in rust was raspberry pi.
  - thecompilr 5y ago
    The post I replied to said M1 only gonna help user applications, not servers, I claim that it helps both.
jbverschoor 5y ago
Just wait 1.5 years and enjoy the apple cloud..
- dreamcompiler 5y ago
  Yeah no. There was a time (early 2000s) when Apple made half-decent server hardware and operating systems. Those days are over. Apple has vocally abandoned the server market, and trying to use MacOS as a server today is an exercise in futility. Too many things require the GUI, and Apple's intense focus on security theater makes everyday server operations a nightmare.
  - criddell 5y ago
    What's an example of something that requires the GUI?
    - dreamcompiler 5y ago
      Allowing full-disk access, turning on sshd, repeatedly clicking "OK" when you're asked "Do you want <freshly-compiled yet unsigned app> to accept incoming connections?" If there are CLI ways to do this stuff I'd love to hear them.
      - criddell 5y ago
        I think there probably are. I know sshd is controlled through systemsetup[1]. sudo systemsetup -setremotelogin on [1]: https://ss64.com/osx/systemsetup.html https://ss64.com/osx/systemsetup.html
  - jbverschoor 5y ago
    I'm not talking about macos.. I'm talking about becoming an energy efficient cloud vm provider.
    - GhettoComputers 5y ago
      What is the criteria to meet energy efficient?
- jlawer 5y ago
  As someone who has worked with Apple "Enterprise" / "Business" / "Pro" products before..... I'll wait. It will start half decent, get a push to 90% of everything you need and then slowly get rewritten simplified to a level that is too basic to do any real work or just abandoned.
chrischen 5y ago
A lot of stuff got prioritized for Arm/M1 compatibility... and fast as soon as the first M1 Macs released. Docker, node, in addition to Apple software.
- MayeulC 5y ago
  > Docker, node, in addition to Apple software. 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.
  - dboreham 5y ago
    Although Node.js existed for ARM, often there wouldn't be pre-built binaries for whatever version/native dependency you needed. M1 has significantly changed that picture.
KptMarchewa 5y ago
Tons of java tools did nothing, until tickets started appearing that X does not work on my dev env.

thecompilr 5y ago

Huh? I am developing natively in macOS for a Linux server using Rust. Everything just runs fine on both. Unless I need to go really low into syscalls I have no reason to be writing and testing my code on Linux.

the_mitsuhiko 5y ago
You’re supporting that point though. A big initial move for ARM in rust was raspberry pi.
- thecompilr 5y ago
  The post I replied to said M1 only gonna help user applications, not servers, I claim that it helps both.

jbverschoor 5y ago

Just wait 1.5 years and enjoy the apple cloud..

dreamcompiler 5y ago
Yeah no. There was a time (early 2000s) when Apple made half-decent server hardware and operating systems. Those days are over. Apple has vocally abandoned the server market, and trying to use MacOS as a server today is an exercise in futility. Too many things require the GUI, and Apple's intense focus on security theater makes everyday server operations a nightmare.
- criddell 5y ago
  What's an example of something that requires the GUI?
  - dreamcompiler 5y ago
    Allowing full-disk access, turning on sshd, repeatedly clicking "OK" when you're asked "Do you want <freshly-compiled yet unsigned app> to accept incoming connections?" If there are CLI ways to do this stuff I'd love to hear them.
    - criddell 5y ago
      I think there probably are. I know sshd is controlled through systemsetup[1]. sudo systemsetup -setremotelogin on [1]: https://ss64.com/osx/systemsetup.html https://ss64.com/osx/systemsetup.html
- jbverschoor 5y ago
  I'm not talking about macos.. I'm talking about becoming an energy efficient cloud vm provider.
  - GhettoComputers 5y ago
    What is the criteria to meet energy efficient?
jlawer 5y ago
As someone who has worked with Apple "Enterprise" / "Business" / "Pro" products before..... I'll wait. It will start half decent, get a push to 90% of everything you need and then slowly get rewritten simplified to a level that is too basic to do any real work or just abandoned.

chrischen 5y ago

A lot of stuff got prioritized for Arm/M1 compatibility... and fast as soon as the first M1 Macs released. Docker, node, in addition to Apple software.

MayeulC 5y ago
> Docker, node, in addition to Apple software. 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.
- dboreham 5y ago
  Although Node.js existed for ARM, often there wouldn't be pre-built binaries for whatever version/native dependency you needed. M1 has significantly changed that picture.

KptMarchewa 5y ago

Tons of java tools did nothing, until tickets started appearing that X does not work on my dev env.