I am using M1 Mac pro and I do code on Ubuntu but I took a very different approach. I have been using cloud-based dev environments based on AWS (potentially any cloud provider).
Different from a couple years back, the integrations of VSCode are now very mature and can provide a very smooth development experience when I use native VSCode + remote server AWS EC2. As you can imagine, when I code on the cloud ubuntu instance directly, the performance on my laptop and the dev environment are both much better because the zoom and chrome on my laptop get more resource and my code also has its own dedicated resources on the cloud. Everybody is happy.
There are a few concerns when it comes to develop on cloud
* Latency:
- after all now every single key-stroke goes to a remote machine will that be slow? The reality is I can't notice it at all. Of course, you need to pick a data center closer to you.
* Computing power:
- Some are concerned the performance of cloud computers. But in fact, cloud computers can be much faster. I once picked a 256GB RAM just for fun. All I can say it, you may want to try it just for fun
* Security
- I will be brief there. Cloud computer is much more secure than personal laptops if you follow the practice, especially if your eng team has lots of remote developers.
> ... while Apple didn’t help port Linux to the M1 (Asahi developers had to reverse engineer everything), they designed the M1 to allow for the installation and booting of other operating systems.
Isn't it sad that this is supposed to be a big deal?
The reality is - https://en.wikipedia.org/wiki/Boiling_frog - that the M1 Macs are now just one step away from becoming a closed system. With Apple ARM chips in the Mac, Apple can now easily lock the bootloaders of M1 Macs any time and make it a completely closed platform like the iPhones / iPads. And it is evident that Apple has been planning this for years:
1. The first few Intel Mac Minis allowed you some level of customisation of both the hardware (change RAM or HDD / SSD) and software (install other full featured OS).
2. Then came the Mac Minis with soldered RAM and SSD. You could no longer customise the hardware. Software was still customisable and you could still install other OSes. (Recall that Apple even offered free drivers for another OS, i.e. Windows).
3. The current generation of M1 Mini now doesn't allow you to customise both the hardware (everything is soldered) and the software. Technically you can install other OSes, but the reality is that currently only crippled versions of Linux and xBSD is available and practically the only full-featured OS available for it is macOS.
These are clear indicators of how Apple has been working slowly to lockdown the Mac platform like their ios platforms. The reason for this is simple - BigTech are increasingly moving towards selling everything as a service. Services are more profitable because it means they create recurring income (even after the device is sold) which means more profits. and Apple's successful business model for this, that earns them billions of dollars, is the closed-platform model that is evident on iPhones / iPads. (Moreover, such closed system also help in planned obsolescence). Obviously consumer rights go for a toss tough.
> Technically you can install other OSes, but the reality is that currently only crippled versions of Linux and xBSD is available and practically the only full-featured OS available for it is macOS.
That's because it's a radically new chipset, not because Apple intentionally hampered other OSes. In fact, quite the opposite: Apple went out of their way to support projects like Asahi. They could have trivially locked everything down, but instead they took extra steps to make sure the door was left wide open.
> ... not because Apple intentionally hampered other OSes ... Apple went out of their way to support projects like Asahi.
Yeah, right - if "Apple went out of their way" to help them, they wouldn't have to reverse-engineer the ARM M1 Macs to figure out how to run things on it. "Apple going out of their way" would be them releasing hardware drivers for Linux or xBSD - you know, like they have been doing for Windows in the past. Developing drivers can consume some resources at Apple and may be too much to expect for every OS platform. But still, if they genuinely wanted to support a multi-os environment, they could make public the hardware APIs so others system engineers could develop drivers for the hardware more easily, instead of struggling with having to reverse engineer everything they are not familiar with.
> They could have trivially locked everything down
Yes, technically, it is trivial now for them to lock the bootloader and completely lock down every mac with a firmware update. But commercially it is not yet a viable move for them as the backlash to such a move would generate a lot of bad PR that would hurt the sale and adoption of the ARM Macs. Apple learnt that lesson when they introduced the Mac Minis with soldered RAM and SSDs - it was the worse selling Mac Minis, and they were forced to step back and reintroduce another model with removable RAMs.
> The backlash to such a move would generate a lot of bad PR that would hurt the sale and adoption of the ARM Macs
You are severely overestimating the potential impact of such a backlash. In fact, I’m afraid the sheer lack of interest in even running other bootloaders is the better reason to expect Apple to continue allowing other bootloaders.
There are good reasons to solder things; it makes things cheaper, smaller, and lighter. These are all good properties to have. The M1 boards are almost comically small and light for what they do.
I'm not overly fond of the non-open nature of Apple (and most Android) hardware, but as long as x86 machines/PCs remain a viable open alternative (still the majority of the market) I'm not overly worried about this; I just don't buy Apple hardware.
99%+ of users both: a) want to run the proprietary OS that came preinstalled on their computer and b) do not want malicious bootkits on their system.
Apple did the best possible thing here.
The iPhone/iPad (on Ax/Mx series chips) is locked as you describe, so the fact that they explicitly designed these as general purpose computers with an escape hatch is great.
That's the best possible situation for the 99% and the 1%.
I think every year for the last 10 years people have claimed the Mac was going to "become an iPhone" or stop running 3rd party code or something and it hasn't happened.
It is happening already happening - I can run macOS, Windows, Linux, xBSD, Android ports etc. on my Intel Mac Minis. But with the ARM Macs, your option are limited to macOS and crippled Linux and xBSD because they can't use many parts of the SoC (like the GPU).
But it is thanks those vocal critics that Apple hasn't been able to go full monty with its plans to fully close the mac platform, and chosen the slow and careful approach to close the system closely, with every iteration. Once the adoption of the Arm Macs reach a critical point, they will close it. Closed ARM SoCs are the wet dreams of every computer manufacturer as they allow them to fully control the system at the expense of us consumers who get locked-in with less and less choice. However, good the Apple ARM Socs maybe, the x86-x64 platform today remains the only viable "open" & truly multi-OS platform for general purpose computing.
>> ... while Apple didn’t help port Linux to the M1 (Asahi developers had to reverse engineer everything), they designed the M1 to allow for the installation and booting of other operating systems.
>Isn't it sad that this is supposed to be a big deal?
Who said this is a big deal? You are the only one calling it a big deal. It is not a big deal. Apple has in the past and is continuing to make booting other OSes possible on the Mac. Business as usual.
As far as full featured, Asahi isn't full featured yet. When was the last time a new Linux port to an entirely new computer design was full featured right out of the gate? Not a useful criticism.
Yeah, wouldn't it be terrible if we all had to run very fast and efficient computers with really high memory bandwidth? Oh the misery. The vast majority of consumers don't give a toss about any of the faux concerns you've raised.
I thought people tech companies mostly bought Mac hardware because they wanted a first class unixy developer experience that you don't really get from Windows even with WSL.
If you feel the need to install Linux on the hardware, why not get a much cheaper and more compatible PC platform where the cost of the OS isn't rolled into the cost of the hardware?
My opinion: M1 gives you (speaking about laptops here): thin and light, very powerful device that runs very cool, a combo that you don't get anywhere else for less money. Frankly it's hard to get close for ANY money. You also get great screen, trackpad, speakers. HW is the reason to get Mac nowadays IMO.
I never went Mac until getting an M1, albeit I did it on the laptop side. Couldn't care less it came with macOS, itd be really awesome if it didnt have to but I'm also used to paying for Windows any times I havent needed it so it wasnt a new experience. It's really just that the hardware is both extremely capable and extremely quiet. Now I can run native Linux on it.
I was wondering the same, from the installation docs [1]:
> UEFI environment only (m1n1 + U-Boot + ESP)
No distribution, just a minimal UEFI boot environment. With this, you can boot an OS installer from a USB drive and install whatever you want (as long as it supports these machines, of course)!
So if the distribution has an arm image then it should work from a usb boot, I’m going to test drive with voidlinux this weekend.
I have the same problem when installing arm64 distos with esxi arm edition. FYI have had success with Ubuntu, Fedora, Suse and even Windows11 aarch64 UEFI isos
I am using M1 Mac pro and I do code on Ubuntu but I took a very different approach. I have been using cloud-based dev environments based on AWS (potentially any cloud provider).
Different from a couple years back, the integrations of VSCode are now very mature and can provide a very smooth development experience when I use native VSCode + remote server AWS EC2. As you can imagine, when I code on the cloud ubuntu instance directly, the performance on my laptop and the dev environment are both much better because the zoom and chrome on my laptop get more resource and my code also has its own dedicated resources on the cloud. Everybody is happy.
There are a few concerns when it comes to develop on cloud
* Latency: - after all now every single key-stroke goes to a remote machine will that be slow? The reality is I can't notice it at all. Of course, you need to pick a data center closer to you.
* Computing power: - Some are concerned the performance of cloud computers. But in fact, cloud computers can be much faster. I once picked a 256GB RAM just for fun. All I can say it, you may want to try it just for fun
* Security - I will be brief there. Cloud computer is much more secure than personal laptops if you follow the practice, especially if your eng team has lots of remote developers.