Live data from Hacker News

Using Apple Silicon (M1) as a cloud engineer, two months in

blog.earthly.dev

11–20 of 103 posts

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#11
post #8

yes cloud engineer yes front end engineer yes senior software cloud dev potato computer engineer yes architectural neural network cloud potato software enterprise senior architect engineer what does cloud engineer even mean?

It's a kind of developer and operations role that focuses on cloud technologies, typically the big three (AWS/GCP/Azure). Why? Do you care or are you just making fun of the job title? If someone wrote "as a Windows Engineer" would you have scoffed?

[deleted]

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#12
Similar experience here. Doing Rails dev at the moment, Ruby, Go, Jetbrains all work great. Using Postgres.app which still runs on Intel under Rosetta, but works fine. There are some Postgres crashes happening intermittently, not sure if that's an emulation problem or the app. Haven't tried native ARM Postgres yet, but heard it works great.

Apps are being updated pretty quickly, and generally makes for a very snappy machine. Comparable to maxed out Corei9/32GB 16"rMBP in performance, but a bit snappier and no fans.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#13
As an outsider looking in, it's hard to take this post seriously. There are biases evident, the most glaring of which is the proclamation that "all of my software 'just works'" followed by a laundry list of software for which beta versions had to be installed in order to be functional at all (including Docker).

It's frankly surprising to me how many hoops people are willing to jump through to use an Apple machine when Docker, arguably the single most important tool many developers use, is just a crappy experience on that platform (ARM or not).

M1 from a hardware perspective is neat, but I am not holding my breath that the rest of the industry is going to move towards ARM for regular old PCs. The only reason M1 is viable _at all_ is because of reasonably fast x86_64 emulation. And that requires special hardware that non-M1 platforms don't have. I suspect Apple would jealously guard against any attempt by a competitor to build something similar.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#14
post #6

Love my M1, but a heads up – if you're dependent on Postgres-based tests running inside of Docker (quite a common usecase!) the performance is completely unusable still: https://github.com/docker/for-mac/issues/5236 We're talking a suite that normally takes 30 seconds taking 10+ minutes.

My solution for such is parallels beta (m1 supported), and arm Debian Linux.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#15
Honestly, I'm starting to understand Louis Rossman's indifference towards these computers. In one of his most recent streams, someone asked him what he thought about the M1 Macs, and he simply responded "it's faster than the last computer Apple made", which summed up a lot of how I feel about it too. I'm saying this as my M1 Macbook Air sits on a shelf collecting dust a few feet away from me, which is definitely not the fate I wanted for it.

I bought the Macbook Air with the intention of using it to replace my aging desktop rig, but was pretty surprised to find that it couldn't drive both of my monitors. Now I had to choose between my 1440p monitor which flickered violently when attached to the Macbook, or my 1080p panel which had a much less disturbing pink line in the bottom half of the screen. After a few hours of troubleshooting, I plugged my desktop in and promised that I'd use the Macbook Air to replace my Thinkpad. At that point though, the value proposition of the computer was so diminished that I couldn't really justify using it. I can't use my OS of choice on it, I can't use my software of choice on it, I can't upgrade or fix anything on it, and I can't trust the swap to not shred the SSD.

Am I missing something here? Time and time again I hear people say "you're not the target audience", and I'm getting the impression they're right.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#16
I kept my old 13" MBP close at hand when moving over to the M1 Air. Turned out I didn't need the old MBP hardly for anything. The recent Go 1.16 in Homebrew was the final piece of the puzzle for me. Docker in preview has been really smooth, especially if sticking to ARM images (the performance alone is worth that).

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#17
> I like bleeding-edge technology, and I had to use preview versions of some software, but had no major issues in my typical workflow.

Those who are in the music production industry would say otherwise, especially those who like using Ableton Live. They got burned on the '64 bit-only' software move from Mojave to Catalina and now they are getting burned again for the hardware move to M1. Not surprised why I see them still running Mojave these days.

As for the developer software on M1, I would rather wait until it is optimised for the processor and the software ecosystem fully supports Apple Silicon before making the switch rather than wasting time finding workarounds that 'sort of work' and ends up breaking in a software update.

Until then, no thanks and no deal. (Until M1X or M2 comes out)

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#18
post #8

yes cloud engineer yes front end engineer yes senior software cloud dev potato computer engineer yes architectural neural network cloud potato software enterprise senior architect engineer what does cloud engineer even mean?

It's a kind of developer and operations role that focuses on cloud technologies, typically the big three (AWS/GCP/Azure). Why? Do you care or are you just making fun of the job title? If someone wrote "as a Windows Engineer" would you have scoffed?

Not if they worked for Microsoft or were in the construction trade. I'd feel the same way about "C++ engineer": are you working on a compiler or do you merely use the tool. I don't know if my intuitive use is more specific than actual practice. After all this also makes sense for, say, a chemical engineer, but would exclude certain perfectly reasonable terms like "mechanical engineer" or "electrical engineer", and "cloud engineer" is sort of like that too.

Of course I know that the GP post was snobbery. Mine is merely a kind of unclear thinking, that perhaps will be improved by reading this thread.

Re: Using Apple Silicon (M1) as a cloud engineer, two months in

#19

Honestly, I'm starting to understand Louis Rossman's indifference towards these computers. In one of his most recent streams, someone asked him what he thought about the M1 Macs, and he simply responded "it's faster than the last computer Apple made", which summed up a lot of how I feel about it too. I'm saying this as my M1 Macbook Air sits on a shelf collecting dust a few feet away from me, which is definitely not…

Honest question, what made you think that a macbook air would replace a desktop computer?
Post reply on HN