- cross-posted to:
- technology@lemmit.online
- cross-posted to:
- technology@lemmit.online
Intel doesn’t think that Arm CPUs will make a dent in the laptop market::“They’ve been relegated to pretty insignificant roles in the PC business.”
Intel doesn’t think that Arm CPUs will make a dent in the laptop market::“They’ve been relegated to pretty insignificant roles in the PC business.”
Hassle?
Not everything runs on MacOS with Arm. Some people may not upgrade to M* class chips, and others who may have switched don’t want the hassle. I know plenty of developers who went to ThinkPads on Linux instead upgrading to M* architecture and having build issues.
Plenty of developers? Ok, sure. It was rocky for less than a year after they released the M1’s. I barely had any issues on my M1 Max that I got at release and I was just thinking the other day about how in haven’t thought about “will this run” or “oh there’s that thing that doesn’t run” in forever.
Yeah, it really hasn’t been a hassle. At my workplace (software research, lots of which is actually x86-specific) many people have switched to Apple silicon Macs and nobody is looking back. The only issue I’ve noticed that is disruptive in any way is that Apple isn’t really supporting TAP based network adapters which causes trouble once in a while, mostly with certain vpn configurations. Standard development tools like IDEs, compilers, etc have worked since nearly day 1. Basically the only common targets that I wouldn’t develop for is Windows, but even then you can do it in a VM and it’s the fastest way to run windows on ARM still.
There’s a lot of brew packages that messed up when the chips came out. It’s still a bit of an issue two years later.