> the issue is not that you can't do it, the issue is that you have to spend extra work at every corner to get things running, because unlike Windows Linux doesn't take your hand and hide all the nasty bits from you, while it tries to juggle a million cases in the background.

You may have to spend extra work to get things running; but once it's done, it runs forever without a hitch.

I know, I use Slackware. It's regarded as a very technical distribution and some manual configuration is expected but once it's done, it's done. I have configs from > 20 years ago that I still use without a hiccup.

I don't know what are these nasty bits windows is supposedly hiding, or what exactly breaks more often on Linux. For me it's exact opposite: my linux just never breaks. I don't do anything special, just plug in the hdd into new box bought when old gets too slow for new tasks, continue as nothing happened.

Uptimes of half a year are not uncommon, the record so far is 400+ days. I just don't shut it down unless there's a serious kernel or hardware upgrade.

It just works, non-kernel updates, stuff being plugged/unplugged, couple times I swapped sata hdds without turning off power (which is simple, they are hotplug by design, just don't drop the screws onto motherboard and don't forget to unmount+detach first).

Now, when I used to and test some cross-builds for windows (win7-win10 era), I had another dedicated windows machine for that. And even though I tried to make it as stable as possible, it was a brittle piece of junk, in comparison.

So in my experience, yes, linux is fundamentally different usage philosophy: you don't need to think about what crap Microsoft will break your workflow with next Tuesday.

Even if we don't agree on a userspace ABI, this is still fine-ish, as long as you can statically link everything you need. Unfortunately the nerds maintaining the core libraries REALLY don't want you to do that, and the answer to "how do I build a portable Linux GUI program" goes more or less like:

"Build musl libc statically, set up a toolchain to use it, build libc++ for that toolchain, get libwayland, link that statically (which their build scripts don't support, roll your own), get xcb,libxau,libxwhatever and build those statically as well, and implement TWO platform layers, dynamically checking for wayland support. There's like 5 different ways to set your window icon. Yes, you need to implement all of them. Now for loading the graphics API......."

On Windows it's a call to RegisterClassW followed by CreateWindowW.

It's an old joke, but it's also accurate in this case - isn't what you are asking for just WINE?

I think that eventually, Win32/WoW64 will be the stable common API for Linux programs - or at least games. I won't be surprised if it outlasts Windows.

> I want a OS where I don't notice that it's there.

I guess you want a Mac. That's fine.

I value freedom and things not mysteriously breaking and functionality not disappearing, and am quite happy investing a the time and knowledge upfront, so I use Linux.

And then there are people who want to have a system which works out of the box initially and who don't want to learn anything and don't mind it breaking later, and they choose Windows.

To each their own.

Everybody "learns" how to use a computer. It's just a question of what they learn first.

> Very, very few people want to "learn" how to use their computer.

I see this point being missed over and over again in this thread. To people like you and I the computer is often the entire point. To normal people it's a tool. It exists to get the job done so they can move onto something else.

The solution that requires the least effort is objectively the best solution. Most of the time that still means Windows, and it won't change until the required level of effort changes.

I mean I kinda agree on what you are saying but then it logically follows that if you don't want to try out alternatives, don't want to push your government to enact better laws, don't want to spend time taking them to small claims court - basically don't want to do anything but suffer - then just suffer.

I know it's a bit ironic given TFA's focus on shoving Copilot and Recall down users' throats, but I really do believe that an OS-level AI agent could solve these usability issues. We need to solve a lot of trust issues, but the capabilities are essentially already there for a non-technical user to tell a Samantha-like OS AI "please get this working", and it will.

Even skipping the first step (which requires a second readme) the next step involves opening a terminal. Instant fail. The entire point of an operating system is to make computers usable without knowing how they work, what a file is, what a command is, or having to look up anything. If something needs to be done, it needs a GUI.

Linux is an important operating system, but anyone under the delusion that it is desktop ready right now needs to actually watch someone use it. I say this not because I hate linux, but because I love it. I want someone to make it usable for a desktop, and people claiming that it is usable right now are not helping that.

That's barking up the wrong tree. Github shows instructions for software developers. A normal user would just install Winapps from package manager, like with all the other Linux software.

Your critique should be channelled into a productive direction and point the finger at the maintainers why this is not packaged yet. https://repology.org/projects/?search=winapps https://pkgs.org/search/?q=winapps

As a VERY long-time Linux user, I agree. Multi-monitor setups, where you can unplug the monitor and have your windows gather back onto your laptop screen requires WAY too much configuration. Having your audio switch back to internal laptop speakers requires homebrewing a script. On my 2020 Dell XPS, I still haven't figured out how to enable the subwoofers - so I'm stuck with ThinkPad quality audio. I have 3 ThinkPads (one with straight ArchLinux, 2 with CachyOS) and there's always some little piece I'm annoyed with. The X1C has good battery life, the T480 and P14s are meh. I JUST bought my first HiDPI Lenovo laptop this weekend. Getting that to be a decent tradeoff between readable text and mongo-duplo-massive UI has been "fun". (Yoga 15.3" Aura edition - I really like it) But running apps in Wine is darn near impossible - the text is for ants!

All of these issues go away with Mac and Windows. I'm not giving up on Linux, I'm just a realist.

Historically I wouldn't refer to it as "bit rot", but generally "registry bloat" with a combination older, no longer used .DLL's hanging around, rather than being removed on software uninstallation or upgrade.

In the past a good "registry cleaner" would help - but those are no longer reliable with newer versions of Windows - there are many virtual entries that get cleaned-up by overly aggressive utilities.

> I had 1 same Windows 10 install running on desktop for 8 years as primary personal PC

I actually have a desktop still running that got a launch party host Windows 7 Steve Ballmer edition install that's just been upgraded as time has gone on. Very much a Ship of Theseus machine but technically only ever migrated the OS image around, never reinstalled. That's 17 years of a Windows install so far, and its perfectly fine. That one install has made it through multiple motherboards and OS upgrades. It'll end up dying and being replaced once I get too uncomfortable with 10 EoL, this board is still useful to me but it doesn't have a TPM so Windows is dead to this machine.

Some of which run better on Linux than Windows.