Live data from Hacker News

Ask HN: How are you dealing with the M1/ARM migration?

news.ycombinator.com

281–284 of 284 posts

Re: Ask HN: How are you dealing with the M1/ARM migration?

#281

The 8GB M1 versions don't have enough RAM for a lot of dev work, doing pretty ordinary things created a lot of RAM pressure when I had one. I later bought Max with 64GB, and that has been brilliant. I gave up on the idea of using Docker almost immediately. Early on there were major issues if you were targeting x86-64 systems code in C++. A lot of common tooling was broken for months on end. Time has solved some of th…

In my wife's case, the 16GB macs don't even have enough memory to drive a 4K display. Her mac goes crazy, overheats, fan at 100%, everything slows to molasses, piece of junk. And it's x86.

Yes, well known, same here on an mbp-16" i9.

For whatever reason the m1 mac's are crazy different. They feel like they have more ram (maybe a faster NVME for swap?), they run the fan crazy less, some don't even have fans (the mac book air). I've heard it speculated they use hardware assist for compression for swap. In any case don't assume that a 16GB M1 will feel like a 16GB x86-64.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#282
post #47

Our entire dev team switched from MacBooks to laptops running linux.

Which laptops?

Does everything work? Special keys on the keyboard? GPU acceleration? Wifi? Going to sleep when you close the lid? Everything "just works" when you reopen the lid? Gestures on the trackpad?

Re: Ask HN: How are you dealing with the M1/ARM migration?

#283
Haven’t had any major issues since switching. Still easily able to get on with my day job and toy around as I always would.

Glad that the world is catching up a little but it’ll take time like anything else.

Biggest issue for me early on was android emulator, once an M1 version was released it was all easy going.

Re: Ask HN: How are you dealing with the M1/ARM migration?

#284
received my M1 last week , my dev workflow is Alacritty->tmux->neovim+lsp+debuggers.Do mostly golang work,installed delve and it went fine followed all steps and compiled from source.Followed same for neovim and compiled from source as i use the lua instead of vimscript. All lsp setups works fine ,unfortunately native delve debugger is not able to communicate with neovim using native back end.As if now for debugging am relying on only terminal based debug not using neovim specifically.In a rabbit hole now as this is neither neovim nor delve so thinking might be new apple arch M1.Not sure if any one else stumbled on the same. with regards to docker as the workplace have licenses i use them with no issue.Entire team is using only mac no other operating system allowed in so safe till now.
Post reply on HN