>Maybe you're just used to your flavors of jank so you don't see it?
That's a throwaway line, everyone is used to their own flavors of jank, even on Linux.
>Your goal is to get off windows, but I've had only Linux on my home computers for ~10 years and it's been working great the whole time, Literally nothing I can think of to complain about.
I think you're trying to read too much into a comment and trying to poke holes...I don't have any Windows, if that wasn't clear. Since we're flexing about experience...I've been doing this since RH 7.2 came in the back of a book 20+ years ago and deploying production Linux services for about the same at a large scale but whatever.
Everything has its flavor of jank, and for most people, Linux is a flavor of jank just barely too far over the horizon still. But, once again, far better than what it ever was 20 years ago, and has the potential to pass Windows at least here soon. But, one of the biggest hurdles especially for adoption is, well, the community, 90% of which think they're one step away from being Linus simply because they installed Arch following a tutorial, and they treat new users the same way for no good reason as they tell the same new users "it's Easy!"
You must be one of the luckier Linux users I guess. I have heard of them, but I've had plenty of convos where once you actually dig into things it's usually not as truthful and playing to the crowd on an internet forum _about Linux_ for confirmation.
>It's been a few years since I had to use OSX for work, but last I used it, you couldn't maximize windows without a 1+ second animation playing when you cmd+tabbed
I use it every day for work, for heavy eng work. Let's be honest, yes there's an animation delay to some degree, but this is trafficking a bit in hyperbole here. GNOME has basically the same behavior for many aspects including switching workspaces by default...which can be turned off in both. The Cinnamon or KDE default experience is better in this regard.
>Docker was also super slow
Only issue I've had with Docker on a Mac with speed is when I'm trying to use some hefty x64 images on ARM macOS (I still have a last model i7 MBA for fun too), which is expected, same with VMs. I've run some pretty gnarly full stack apps, some that included Java backends that needed up to 8gb because reasons, without issue as long as I built an ARM image.
>There's no package manager and the usual recommendation (brew) for a third party one is trash that will update programs you didn't ask it to when you're installing something else.
It behaves roughly the same on macOS as it does on Linux, IME. If I'm not explicit on dnf/apt, I get more updates than just what I wanted too. But maybe I'm missing something. It's how I manage all my tooling on the work env and gives me very few issues save usually for only the occasional connection issue which is always attributed to work VPN nonsense.
>IIRC external monitors are completely unusable from blurry text.
Even on a Mac? The ecosystem is designed for professional graphics use, never had an issue there even back to CRT days heavily using all the Adobe suite versions, and even with non-Apple displays. Every Linux setup I've ever used, including this one is janky with external monitors, let alone dual. Even the "Easiest distro in the world" (Mint) according to most Linux nerds is problematic to say the least in trying to use the screen res/layout settings.
>I used a windows laptop recently for a year or so for work. Absolute jank. Sleep was just broken. Like wouldn't sleep/spin down the fan with the lid closed unless I unplugged it. Often completely frozen requiring hard reboots when opening the lid.
A - agreed, I don't work anywhere which requires Windows, because for all my devtooling, it's all tied into a macOS ecosystem, yes, with homebrew for now. Been that way for almost a decade now. Ideally, one should also do a lot in a build container for 1:1 matching so your CI jobs run the same env/toolset/versions. It's better for real dev work and way more stable in a way that won't require you to become a support headache for the company either.
B - what you are describing is a hardware issue and attributing it to Windows. I had the same issue on a B550 series desktop mobo, went to Linux, same exact behavior. This is not an OS issue.
>Leaving it "sleeping" for an extended period would still heavily drain the battery.
To my mind, non-mac laptops are garbage for battery life, everyone knows this, and yeah if it wasn't sleeping for real it's gonna eat up resources. This is more a hardware issue than anything, not the OS layer. Put Linux on it and I could almost guarantee you would have had similar issues, I've dealt with this like I said w/ the mobo above.
>WSL barely works. For some reason I have to care whether things are in my Windows or Linux home directory. Wrong one and git commands take seconds. I'd get environment mismatches where the terminal in VSCode would fail to run commands that run in a normal CLI, etc. DNS would break inside WSL because it wouldn't propagate config from DHCP. UI is just slow to respond to anything. If you start typing in the start menu search (e.g. "shut down" or "power off"), the menu replaces itself with a different one, and you can't find the power options until you close and reopen the menu.
Man, I have to wonder....was this not using latest/WSL2 and instead using WSL1? Because there _is_ a massive leap between the two. It's not ideal compared to native on Linux or even mac but still works quite well for many use cases. When the WSL2 upgrade came back when I was forced in a past env to use a Windows laptop, myself and 4 other Devs could run our full stack including Kafka locally without much issue on WSL2 other than producing heat on the laptop b/c of how many services we were running. (About 35 .NET Core microservices at the time, along with redis, Kafka, etc.). Yes, the home pathing was a tad annoying.
>If you start typing in the start menu search (e.g. "shut down" or "power off"), the menu replaces itself with a different one, and you can't find the power options until you close and reopen the menu.
Yeah every OS seems to have issues with their search/launcher tooling, but the Start Menu has been shit for a while now. I've had more issues on Windows than anything else re: manu defaults (once tweaked on like W10 it's fine), but then Linux, and then even macOS...before paring down Spotlight to only search certain things, which made it way better.
shrugs
I think this is one of the challenges of building good software, it's why Apple does what they do. Some experiences on one hardware set are somehow perfect, but they're rare, some are the exact opposite. But a lot comes down to what a user is willing to tolerate, too, and while someone might say it was "Easier on Linux" it's usually just that they're willing to tolerate more terminal madness and odd behaviors than others in their daily driver.
