I’ve also had a lot of success on most hardware, but the worst device I ever touched was a 2016 Macbook (one of the last with normal ports) and that thing was a total mess.
Arch: Video, no sound.
Debian: Sound, no video.
Ubuntu: Everything works, reboot, nothing works.
Probably heavily related to hardware, but still, very inconsistent. I was never able to find the actual issue after weeks.
The final somewhat working configuration was Debian+Liquorix for the video firmware.
Well, that may be the case, but you made the claim that using a beginner-friendly distro solves all problems and I gave an anecdotal example of that not being the case. Macbooks have a substantial markt share, like it or not, and are subject to planned hardware obsolescense, so people will try to install.Linux at some point.
Besides of all, this was not purely a hardware issue. Else, no configuration would have worked out. There were differences in the default configs of the distributions that caused this erratic behavior and it was not just a pulseaudio/pipewire thing.
That’s not true.
I’ve also had a lot of success on most hardware, but the worst device I ever touched was a 2016 Macbook (one of the last with normal ports) and that thing was a total mess.
Arch: Video, no sound. Debian: Sound, no video. Ubuntu: Everything works, reboot, nothing works.
Probably heavily related to hardware, but still, very inconsistent. I was never able to find the actual issue after weeks.
The final somewhat working configuration was Debian+Liquorix for the video firmware.
So no, it’s not guaranteed.
What do you expect from a Mac, a company whose entire ethos is proprietarism?
Nice catch! 👏 Using one of the most proprietary devices out there in the market as an example.
Well, that may be the case, but you made the claim that using a beginner-friendly distro solves all problems and I gave an anecdotal example of that not being the case. Macbooks have a substantial markt share, like it or not, and are subject to planned hardware obsolescense, so people will try to install.Linux at some point.
Besides of all, this was not purely a hardware issue. Else, no configuration would have worked out. There were differences in the default configs of the distributions that caused this erratic behavior and it was not just a pulseaudio/pipewire thing.