- Webcam on MacBook Pro (some dude reverse engineered it but I packaged it into dkms .deb so I didn't have to compile every time I updated the kernel)
- vpn through company firewall (which didn't support Linux, and wasn't openvpn compatible, took absolutely ages to get it working)
- getting the thing to properly sleep, wake and not chew the battery
- fuck Nvidia and Lenovo (different laptop)
I still prefer Linux and use it as my daily driver.
I'm cherry picking here but in this case you're just doing your company's endpoint management job for them.
This was my last job and I have also spent a lot of time packaging and scripting (for autoconfiguration, I don't like presenting the end user with technical questions if we already know the answer to). On entirely supported platforms.
This kind of thing is a full time job in many companies so if you go outside of the supported path and do your own then obviously it's going to take considerable time :)
This is a recurring theme with Linux, because guess what, many companies want nothing to do with desktop Linux, for better or for worse.
So you'll have to do their job for them, as a side gig.
I agree the focus isn't there. I was managing everything "not Windows" as an endpoint architect and it was very difficult to get other teams to consider them. Makes sense because "not Windows" was less than 1% of our userbase. So I had to really push for them to select tools like VPN and antivirus that support Linux and Mac.
However we did manage. What I did see a lot was that R&D users didn't want to use the standard supported distro (which by the way I picked with their input). They complained about all the mandatory antivirus software (which was not my choice, but the security team's mandate). But really there was a very high amount of "I just want to manage everything myself" going on too. You can't have it both ways though. Either you get a managed endpoint and you have to roll with some of the decisions or you do it all yourself (and in some cases are locked out of some critical environments due to security policy)
This is fine (well fine by me, but not by our security team!) but then don't complain about how hard it is to get it set up.
I can see how WSL fits well into this for companies, though I prefer real Linux myself too. A lot of R&D users would be on Mac as it's a "Linuxy enough" OS with much less hurdles in a corporate environment (native MS Office available etc).
I dont remember exactly but i think it was Fedora 25 or 26 (or around there) where they removed some symbols because some fucking moron thought "they arent used by anything" so they pushed them to torvalds linux repo. And the changed got accepted.
You know what used them? Nvidia drivers.
So after a couple of hours fixing that, which at one point started involving rebuilding the kernel and other things that a normal user shouldnt have to EVER do, i just said fuck it, and installed Windows. That laptop is still running decently as a browser/media player at my folks
Now im just using a Mac as a day to day pc, and a windows laptop for gaming.
Even if i deal with Linux at work on servers, and with containers and stuff, i'll never go back to linux.
Windows does not have a proper central packager mechanism so if you let it, your software will get really ... floppy.
I spend way more time doing stuff on Linux than I ever did with Windows. Windows software comes from so many sources and it takes ages to find it and update.
- Battery life was terrible compared to Windows (usually 3-4 hours, compared to 8 on Windows).
- The trackpad/trackpoint would often not come back after resume.
- The fingerprint scanner usually worked 20% of the time (while it always worked on Windows) and when it failed, you had to wait for a long timeout, because there is an issue where when IIRC PAM is performing authentication with one module (fingerprint), it cannot support simultaneous authentication through another method (e.g. password authentication).
- I had a Lenovo USB-C Gen 2 Dock, which worked great on Windows. On Linux, the lanes were misconfigured and HBR3 was not enabled, so it was not possible to use an external 4k screen with 60Hz.
It was the full Linux laptop experience as I remembered it. I decided to buy a Thinkpad after using Macs on the desktop for ~14 years. I had really good experiences with Linux on my Ryzen workstation as a desktop, so I thought it might be time to switch on the laptop again. Now I am fully back in Mac territory and probably won't try Linux on a laptop for at least another 5-10 years.
I could have kept the laptop since Windows worked very well. But my brain is just wired for Unix, so no dice.
I've installed various Linux distros on many laptops, and even though I could usually get everything working, the deal breaker for me was often battery life. I wonder what kind of battery life the people with RHEL on a P53 are getting.
I never really got battery life anywhere close to windows or macos and my T480 has an extended battery which weighs a tonne.
Every time I do an update on the Linux PC it always breaks a bunch of things and I typically have to spend 4-12 hours to fix everything.
But the good thing is that I can usually fix everything, and after it's fixed it will stay that way and work reliably for as long as I want until I choose to do another update.
I still love Linux, the only reason I'm using Windows at all is for certain software that doesn't work on Linux (Ableton and games, also no HDR support in Linux).
Recently did an update from Ubuntu 16.04 to 18.04, which completely broke lirc which is the program that runs the IR remote.
So my unhappy partner was unable to use the remote in kodi until I finally worked out how to fix it (and every aspect of how they broke it).
Looks like they just changed the way it works for no useful reason. I had to manually set up every IR button again because the remote name had changed from "mce" to "devinput-32". Why??
MythTV didn't work at all because for some reason the mysql bind address had changed so it couldn't access its own database.
Once I got that working, I discovered that the remote didn't work in mythtv either. They had changed the name of the ?file? they use to send button names. I had to make a symbolic link to the new name so the remote would work in MythTV. "sudo ln -s /run/lirc/lircd /dev/lircd". Why??
Also I had a button set up on the IR remote to shutdown kodi. That stopped working and took me more time to fix.
Kodi was also throwing some python errors, fixed by doing "sudo apt install python-backports.functools-lru-cache"
The Kodi database also got corrupted somehow, so some files weren't showing up until I deleted the database, which meant I lost the resume times on videos we were watching. I spent a fair bit of time googling and trying to fix the database but in the end, no matter what I did those files would not show if the database was active on my movies folder.
Also the Nvidia drivers needed to be reinstalled, but I expected that because that breaks with every single update.
So yeah, that was about a week of evenings to get it working back the way it was.
Most of the other issues IIRC were annoyances more then anything else.
For example Lenovo maintains a list of support laptop versions, and which Linux distros are certified on them. I believe Dell and HP have something similar. Just stick to the supported hardware/distro combos (well, you can typically run whatever distro but at least you have a good baseline), then you should be fine.
None of that was enough to push me away from it, but those problems would also exist on a custom built desktop with fully supported hardware.
It was a passionate love/hate relationship.
To be clear: I consider your (and other people's similar) experiences completely valid; I just wonder where the differences are. You see something similar with people reporting experiences with Debian/Ubuntu vs. Arch/Void etc, where some say one worked horribly for them and kept breaking and the other was very stable, and others report exactly the opposite!
The only serious issue I can recall was on my very budget HP laptop I got in a bind where the WiFi didn't work as Realtek didn't upstream the drivers for that when I got it (they did after a while), so I had to manually compile and load them: not something I would expect someone without Linux experience being able to do. Other than that, everything (Bluetooth, webcam, WiFi, sound) has worked fine on two Dell XPS's, that HP, and four ThinkPads for about 15 years now (although there were undoubtedly issues that I have forgotten about, none of these machines stood out as "problematic on Linux").
When you feel like you have all the time it isn't an issue but after I barely got away from a very busy and very long work and all I want to do is rest for 2h and watch some entertainment or edit some document/form or even keep up with a hobby project and Linux eats away my evening/weekend, that's a different experience.
But I still like Linux a lot, the community makes it worth the fight.
But this was to do with Software I was working on requiring legacy versions. I found that docker got rid of this.
Every now and again something would happen and I'd have to fix something after an update but it was very stable. I'm finding administering a Windows network is much the same. Microsoft just released an update that nuked my SMBv1 shares. So I had to fall back to SFTP. I probably should have been using that all along as it allows for a much more secure network.
On the other hand, the annoyances from Windows (general sluggishness, pop up advertising, Explorer never remembering how I want things viewed, etc) are now really starting to outweigh the annoyances on Linux, so ultimately I don’t think it matters.
What did you spend that time on? I never need to look at anything; it's a big reason I use Linux: my system today is the same as it was yesterday, and last year. And will be the same tomorrow, and next year. Of course Firefox and the Linux kernel and all these tools get updates, but overall it's pretty stable from my user-visible perspective. I certainly don't have upgrades which completely change the UI like Windows 8/10/11 "forced" on me, and if something does go wrong (which it rarely does), I can usually figure things out – Windows: not so much.