This is one of the primary resaons I ditched Windows for Macos.
The multitasking on Windows is ridiculously bad.
Also, applications that freeze and can't be killed/restarted are simply part of life on Windows.
Add to all that, Window slows down over time - again, the periodic reformat and rebuild is part of life on Windows. After I switched to Mac I didn't need to rebuild the operating system essentially ever.
Also, the registry - I think the worst idea in all computing. Prior to the registry you plopped a windows application in a location and configured it with an INI file. After the registry the entire operating system and all applications turned into one big ball of chewing gum, glue and hair dredged out of the shower drain.
Anecdotally, that's not my experience with Windows these days at all. I've never had the whole system freeze up on my Win10 desktop. Never noticed a slowdown or app that can't be killed, and never done a reformat or rebuild. Windows Update is mildly annoying when it decides to reboot your system for you, though usually when you're not using it. The registry seems fine to me too. Okay it's not perfect, but I don't think it's meaningfully worse than the MacOS or Linux system of configs in text files with various types of special formats all over the place, unless of course it's some kind of binary format that can only be modified with a special CLI program.
I agree. Windows is basically fine these days. It's even better than Mac and Linux in a big way from a desktop stability point of view because it has the Ctrl-alt-delete interface which works reliably and lets you kill the offending program.
Linux has various useless options like sysreq shortcuts that you can't remember and kill random processes, and I don't think Mac has anything, though to be honest I don't recall ever bringing a Mac to its knees so much that I couldn't open a terminal and run `top`.
I wish Ctrl+Alt+Delete would be reliable enough to work with full-screen games. But, half the time, when you try to launch Task Manager that way to kill the offending process, it ends up under the game's output. I've learned to kill processes using keyboard navigation by looking at Task Manager's thumbnail in Alt-Tab process list, but it's ridiculous that we still need to do this kind of dance in 2023.
In my experience, on macOS the Cmd-Opt-Esc force quit dialog works pretty well most of the time. Of course `killall "Foo"` in the terminal works nicely too.
Until the advent of the new screen manager, you could always reliably get to a VT terminal.
Full io access and unlimited kill power, far better than ctrl alt delete...
Any regressions in this area I blame on systemd, which I think runs on cpp, so you know I blame cpp... (kernel is written in c, windows got a bit better when they used c# instead of cpp, Mac never used cpp...everybody kill cpp, quick)
Systemd is certainly not implemented in c++. I don’t think many of the authors are even well familiarized with the language. Look at the chart at the bottom of the project page.
I make a full+incremental system disk backup periodically, e.g. once a quarter or two, or when I feel that a set of software that I'm going to install could do something bad, or after big changes which are undesirable to lose in case of failure. It doesn't save everything (important data is in git remotes anyway), but saves me from a reinstall-download-setup-reconfigure hassle. A user folder has a separate automatic and more frequent schedule.
That said, my home PC works since 2018 (buy date) and one at work since around 2016. Only used these backups once to move OS to a new SSD.
Most failures happen when you have no backups, so have at least one to make your system failsafe!
I have multiple irreversible-damage experiences with linux too (not bsods, but think of updates and/or nvidia drivers). Even 18.04 to 22.04 transition on one of my older vpses failed recently despite absolutely default setup. I’m fine with MSYS2 as a unix-like env.
I’m not sure what “multitasking is bad” means, but I do a heck of a lot of multitasking on windows every day with resource intensive developer tools with no problem, and have been doing so for over a decade.
Apps can be killed via task manager without doing anything special. You might run into an occasional rare bug where explorer freezes so you can’t open task manager, but I can’t recall the last time it happened to me (and you can’t tell me with a straight face the Linux or MacOS are completely free from wild edge case bugs of that sort).
I used to religiously reformat and reinstall windows. It’s been completely unnecessary since at least Windows 7. My personal desktop ran from 2014 to 2021 on the same install, including a Win7 -> Win10 upgrade.
You certainly may not like the registry, but it’s hard to make a compelling argument that it’s been a source of problems since Win7. To be honest I think all of the registry problems I can recall seeing in the last decade were caused by people being sucked in by “registry cleaner” scamware/malware apps claiming to fix non-existent problems.
Same experience here. I work my machine hard. It runs 24x7, hosts many sites, databases, Plex, and I do some pretty heavy development work on it daily. It pretty much "just works". The last time I had to routinely reinstall Windows was Windows XP. Ever since Windows 7 driver stability is significantly better. Despite all the bad press, the Windows 11 upgrade was smooth for me. Yes, the OS has some annoying features, but all in all it's been remarkably stable.
Switching from FF to Chrome (this was like a decade ago, to be fair to FF) eliminated about 50% of my beachballs and other unresponsiveness system-wide, not just when using FF. Switching from Chrome to Safari got rid of almost all the rest, and also made my battery life match Apple's claims.
[EDIT] And when I do still run into trouble, it's almost always Electron chat apps. Slack, Teams, and Discord. All terrible at being respectful of system resources. Closing the program and restarting it usually temporarily fixes the problem, but that shouldn't be necessary.
It's frustrating that efficiency and being a good desktop citizen is such an afterthought for most browsers. Support for all the fancy web features imaginable is isn't worth much to me if means keeping my system pegged and destroying its battery life.
Afaik browsers are highly efficient and a lot of work goes into optimization. On the other hand, they're expected to run arbitrary code (JavaScript, Web Assembly) which can do all matter of terrible things. A couple years ago, it used to be Gmail/Google Voice websites would take nearly 1GB of RAM alone per tab and crash if you left them running a few days.
A website could just run <download big json blob and append to array> in a tight loop and the browser has to try to make decisions on not hosing website performance if the user wants to actually use the crappy website while simultaneously not hosing battery/machine performance.
Blink and Gecko don’t fare as well as WebKit does when it comes to efficiency which would suggest they’re making tradeoffs favoring things other than battery life.
things have improved a lot over time. I have one project involving json arrays that grew way out of hand. Sort of panicing about the need for a fast 80% rewrite while not having 10% time I tested a good number of devices. Crappy androids and low end iphones deal with the many thousands of objects incredibly fast. I still think its wrong I just have nothing to show for it.
ff a decade ago would just randomly die on me within 2 days.
A very unreasonable reason for me not switching to Safari is because the bookmarks dropdowns (when activating the bookmark bar) have two very annoying features. Firstly they only open when clicked, so if you click one and move your mouse to another, the other doesn't open, just the original stays there and you have to click off it to close it. Secondly there's some kind of delay to that click such that if you accidentally click the wrong folder of bookmarks, click off it to the correct folder and click again to open the correct folder, if you click too fast it'll do nothing - no opening the new folder, nothing. And it'll continue to do nothing if you continue to click 'inside' the timeout window. So you have this artifical delay built into bookmark navigation that just put me off.
That and also ultra-wide tabs which change in size as you close them with a middle click, which is really annoying and you sometimes close the wrong tab. Close them with the cross and they stay the same size and neatly collapse, you can even then middle click to close the remainder and they stay the same size. Silly difference in behaviour IMO.
It's the little things that put me off. Shame, as Passkey support is great.
A decade with Ubuntu and I get why it’s free. I have disastrous performance issues with it, for reasons that people usually respond, “oh well that’s not Ubuntu’s fault…” but that isn’t a great excuse as users do not care (unless you aren’t intending to attract general users).
Most of the issue is that I have to fight with nvidia video drivers every month or two. Something happens and they stop operating and it grinds my entire system to a crawl when everything is software rendered. YouTube basically kills my computer.
When I go with Mac or Windows, the main feature is that they have designers to make more than a Potemkin UI, and they care about the end to end UX. No, “oh go complain to some other vendor.”
Ubuntu is very very impressive for free. I certainly acknowledge how great that is, and how important that is to the ecosystem.
The wild thing is that using the Additional Drivers UI is what bricked my computer last week. It probably downloaded some binaries but it also spent 30 mins running gcc compiling something. And then forced a kernel headers update but didn’t update anything else. Rebooted and I have no wifi or bluetooth.
The fix was a reversion and then CLI install of the nvidia 515 drivers.
Imo Intel graphics work best (not sure about the new dedicated GPUs) if that's powerful enough for you. I've had some issues with amdgpu although no special setup is required. Unfortunately a lot of hardware manufacturers are Windows first (and only) and some poor volunteer has hacked up a Linux driver via reverse engineering
If you want a good Linux experience, you should look for hardware with first class Linux support. Likewise, good luck with macOS on non-Apple hardware--it's possible but ymmv
The trick is to disable automatic updates once you have a working system. Yes, there is some risk. But at least your system will stay as stable as it was when you first installed it. Oh, and disable swap and have plenty of RAM.
32GB + swap off really does help for sure. I do have updates disabled but I admit I am sloppy with not picking through what I update. It doesn’t help that there’s new updates basically daily.
Thats a good description for many linux GUIs. They look like they can get the job done, but to really get the job done, you have to use what the developers of said UI likely themself use - the terminal.
A friend used the term when I said, “I used Additional Drivers to update to the latest recommended driver and it bricked my computer.” He said never to use that UI and to do it via a terminal. The terminal approach worked effortlessly and in half the time, once I Un-bricked my laptop.
It feels like a lot of the UIs in Ubuntu are there just so they can claim it’s an OS that can take over for Windows or Mac.
My own personal experience (recent x86 based MBPs and similar) is that macOS degrades quickly when CPU and IO get stressed, but Windows 10 and 11 become unresponsive with much smaller loads. Of the big three, Linux is the one that can take more processes while still being responsive.
Even a lowly old i3 can encode videos with ffmpeg while you browse the web provided you start ffmpeg with a `nice -n 19`. On a Mac, it seems to be ignored.
Linux UI actually becomes very unresponsive under load (on most distros) because the default kernel scheduler is tuned for throughput at the cost of responsiveness, instead of vice versa.
Desktop distros switching to a more user-friendly scheduler, and loading a ‘small speaker’ EQ via Pulse on detecting internal speakers (= laptop) are two massive, low-hanging fruit improvements for Linux that just don’t seem to be done.
2019 13" MBP, 16GB. Pretty much anything I do will spin up the fan now. Compiling an app uses so much battery that I get less than an hour of battery life. I've resorted to remote development only, a la Chromebook.
My previous laptop was a similar Lenovo X1 Carbon with Debian and wow do I miss it, but I don't have too much of a choice since I do mobile app development :(
Yeah, the 2019 MBPs were absolute abominations. I spent 5k AUD on a fully kitted out MBP and performance wise it’s one of the worst computers I’ve ever owned.
I swore that would be the last Apple computer I ever bought, but then they released the M1s… and they are very good.
Would recommend getting an M1 if at all possible. There’s still time to ask Santa for one.
I recommend getting a Framework. It's probably not as good as an M1, but it'll last you more than two years, and if it doesn't, you can just change the CPU for a better one without having to throw all the other, perfectly good hardware away.
my macs absolutely start to degrade after about 18 months, and I try to keep them limping along for a few more months. I think it’s usually the battery crapping out that causes everything else to sort of overheat and suck
I had my 2012 MacBook Pro for 8 years, before giving it to my dad where it continues to be used (though under far less load than when I had it).
I did get the battery replaced once, it was free. The screen got replaced twice, also for free (the second time they just did it when replacing the battery because the person at the Apple Store noticed a slight wear on the edge anti-reflective coating)
> I recommend getting a Framework. It's probably not as good as an M1, but it'll last you more than two years…
Macs have famously-long usable lives — my sister uses a 7-year-old iMac, for example. The latest macOS Ventura supports Macs made in 2017. I'd be very surprised to hear about people using 2021 Framework laptops as their daily driver in 2026.
I've had 3 MBPs, every single one has had at least one issue, well before 7 years, usually around 1.5 to 2. The first two had battery recalls, the middle one had cable-gate, the middle one's display was also very temperature sensitive (it would have glitched lines artifact on the screen if the ambient temperature wasn't near 70F), the later MBP suffers from keyboard-gate and from constant thermal throttling. (Likely because the vents are choked with dust, but MBP's user hostile design prevents me from opening it up and pushing air through it, which is likely all it requires. They hate the user so much they used screws worse than Torx. I think they're Pentalobe, but don't quote me.)
My current Magic Trackpad is also highly temperature sensitive. The "click" will lock up at high temp. (I.e., the trackpad will fight you, if you attempt to click, if the ambient temperature is warm.)
> I'd be very surprised to hear about people using 2021 Framework laptops as their daily driver in 2026.
I'm using a Lenovo Thinkpad at about that age. (It is a 2017 model, so, 5 years.) The biggest thing wrong with it at present is it requires AC power. (The battery connection is bad. It lived through two bike crashes, though, and I suspect that's a side effect of it. I should see if that's repairable, one of these days, but I've put up with that for the time, as with COVID, it doesn't really travel much anymore.) The TrackPoint™ is also wonky, but I think that's because sunlight has chemically hardened the nib like an old eraser. I have more nibs… somewhere. I should look for them or order more…
It would be absurd to claim that Macs don't fail or need servicing during their usable lives, but you seem to have been particularly unlucky in my experience.
> They hate the user so much they used screws worse than Torx. I think they're Pentalobe, but don't quote me.
But you're in a thread about how the GP's Mac didn't last two years. I'm fairly sure I will be using my Framework laptop as my daily driver in 2026, maybe with one motherboard replacement. I just switched from my 2017 XPS, and I do development work. I gave it to my dad, who loves it and will probably hold on to it for another few years.
It's a bit odd to be saying this about pre-M1 Macs, as they were "just" Intel machines, same as everything else.
An M1 Mac should last double that, easily - so long as you don't underspec it. My family has multiple November 2020 M1 MacBook Airs that are still working good as the day we got them.
Frameworks are nice in theory but they still have a long way to go when it comes to heat, fan noise, and battery life based on what I've seen owners of them say.
This is the biggest reason that I won’t get a Framework today. Give me a Ryzen with 8+ cores, 32GB DDR5, hopefully two m.2 slots, a full-size HDMI and USB-A port(s), 99wh battery because of TSA security theater, dedicated graphics, and some real heat sinks that can handle 200w+ so it doesn’t have to run the fans constantly or cook the touchpad. A 4:3 OLED with at least 4K resolution and 120hz refresh would be perfect on top. Ooh, and a rigid chassis that doesn’t flex like a noodle, and no RGB / gAmER tacky plastic junk all over. It’s sad that a package like this is very rare.
I have been where you are, posting the same thing, but I don't believe it is true today. Applications that hang and can't be killed is a much bigger problem to me in Linux than in Windows 10. I also don't reformat, at most i reset Windows or applications but it has been years. I agree with the rest but in everyday use the registry is not a problem in Windows.
The difference to me is that I as a power user might be able to fix it myself in Linux but by only using the tools normal users know of I must say I cannot recognize that this is a weak point in Windows today. Clicking the X to close an app and getting stuck with a dead app is much worse in, say, Debian than in Windows.
With that said.. I don't use Windows where I have a choice but that is mainly for philosophical reasons these days. Mac I don't touch. I feel it is the worst of both camps.
On Linux, processes that are stuck in D state (waiting on I/O) cannot be signaled. More specifically, the signal will be queued until the task exits that state. This includes signal 9.
The process may well never exit that state, for example if the I/O it's waiting for is actually over a networked filesystem and the NIC is misbehaving.
I wrote a long comment on my phone telling you how this is simply untrue.
During the typing of the comment, Safari locked up and then hard-crashed, losing my comment.
If that happens on something as tightly-controlled as iOS, how many bugs and crashes do you think macOS and it’s apps experience?
The main difference between macOS and Windows or Linux, I’d say, is that bugs on macOS are more submarine. Windows also has much stronger recovery mechanisms, to the point where a GPU crash barely phases it. A GPU crash on macOS will hard-reboot the system and possibly show you a ‘:-)’.
When the Intel Mac arrived, so maybe 14 years ago or more?
Are you saying Windows has fixed all these problems?
The registry is still there.
I do actually have some Windows machines I use sometimes and recall thinking "still the same" but I can't say that as a hard core user, so I'd be interested to hear if Windows is now a sleek, reliable multitasker that instantly kills dead applications. Nothing will make me OK with the registry and the general mess of Windows though - it's like a house someone hasn't properly cleaned for 40 yeaes.
I feel like if you're bothered simply by the existence of the registry, Windows isn't really for you. I get it, a little bit -- the OOM killer on Linux just boggles my mind, but once you view in context, you can appreciate how we ended with it, at a technical level.
But if you think the registry could be replaced with .ini files like the good ol' days, that's a pretty extreme hot take. If you're open to changing your perspective on what the registry is for, how it is designed, and why it's necessary, read any of the Windows Internals books.
I certainly get a lot less blue screens and lockups than I did in the past, and the OS shuts down locked-up apps more quickly.
Group policies have replaced the registry for advanced configuration of the OS. The only time I’ve needed to change the registry is for dealing with poorly written, old drivers, which are becoming more rare as Microsoft’s standards for getting a driver signed are becoming more stringent.
> Add to all that, Window slows down over time - again, the periodic reformat and rebuild is part of life on Windows.
My windows install is from 201*, it was an upgrade from win7, and switched from an i7 to a ryzen. I do clean out the registry/startup/task scheduler on occasion.
One of the IBM 1401 computers (1959) at the Computer History Museum has hardware support for pre-decimal pounds/shillings/pence, to perform arithmetic on these values and print them. Thus, the computer has three fundamental datatypes in hardware: arbitrary-length strings, arbitrary-length integers, and pounds/shillings/pence. Of course there were two competing standards for encoding pounds/shillings/pence, so the front panel has a knob to select the standard.
(Before decimalization, there were 12 pence in a shilling and 20 shillings in a pound. Mathematical operations on currency were both difficult and extremely common, so IBM provided hardware support as an option. There were boards of transistors so you could add, subtract, multiply, or divide currency values with a single operation, rather than an inconvenient sequence of instructions.)
To get back to the original topic, I'll mention that my MacBook Air would drop keystrokes if I visited a website with, say, a video ad. I find it kind of appalling that computers in the 1960s could handle input from hundreds of keyboards at once, while a 2017 computer can't manage a single keyboard.
In the defense of your Mac, computers of the 1960's had terminal controllers for dealing with the communications. And 3270's were like web browsers - getting a form, sending the data back, getting another one - an excellent design for avoiding hardware interrupts ;-)
But yes. I've seen 370's with a good couple hundred 3278's connected and that thing was still quite snappy, even though the CPU in my watch can run rings around it. I guess even two VT330's would stress my current laptop if I could type on two keyboards fast enough ;-)
The widespread adoption of CISC architectures solved this problem, since many of them included special-purpose BCR (Binary-Encoded Roman) instructions.
I think all desktop OSs have it wrong. Allowing full APIs to backgrounded apps and no CPU reservation for control apps will ultimately end desktop computing - we’ll create on iPads because they work.
I'm writing this on an old i3 and it feels perfectly fine. It would probably take days to compile a large project like Chrome or LibreOffice, but, as long as I run the make under a nice, I can continue using the computer and the only sign something big is happening will be the CPU fan kicking in.
Regular users don't understand CPU quotas. It should be done by default. The current behavior on Windows/Mac/Linux of allowing a program to make the machine uncontrollable is poor.
This will probably change as we get more cores and performance/efficiency ones. Macs already run a lot of the low-priority tasks on their slow cores leaving the fast ones available for interactive activities.
I don't disagree on the current approach though. If I start a, say, long build job from a terminal window, I have control over the resources it can take. If, OTOH, I start a program from the GUI, it's reasonable to assume I want it to have full control, at least while it has the focus.
Now, letting the GUI dynamically renice non-focused processes would be very nice.
More cores won’t fix it. Some app will add more processes and use all available CPUs and there’s no reservations.
You had it right with nice - phones and tablets and consoles and cars have it right with their techniques. Apps shouldn’t be able to make the system unusable by default.
By themselves, no, but there are limits to how many cores a workload can keep fed. You'll see declining returns at high core counts (which is one of the reasons we don't have Xeon Phis these days).
> This is one of the primary resaons I ditched Windows for Macos.
The raison I just ditched Fedora for ubuntu...
The raison I ditched MacOS for Windows is that MacOS is slowly but surely becoming a magnified version of iOS... One day you will have to jailbreak if you want administrator rights on your ~~personal computer~~ Macbook.
Don't MacOS and Unixes have the equivalent of registry hell with a million configuration files hidden away in /etc/ or /usr/ or wherever, and then having to check where environment variables are set and so on? Ideally, almost all of a program's configuration settings would be stored in the same folder as the program, readily discoverable, and you could just pick these things up and move them easily, but in practice, it seems to be a pain everywhere.
The registry is uniquely crap because it puts all the configuration for everything into some single store - I don't know what devilish format lies beneath it, then it stores everything as binary keys. Things are not separated strictly by application so you end up with a giant pile of intermingled goo.
In Linux, no doubt there's alot to get your head around, but I've never found things to be a giant pile of spaghetti. The challenge Linux has is there's a bajillion ways to do things so you have to be pretty experienced to feel confident crawling around the tunnels and ventilation ducts.
The disfigured nature of the registry is a real shame, I actually like the idea of centralizing all configuration in Windows. I wonder if there was a better solution in Cairo.
To be honest (and I'm aware that I might be tarred and feathered for this) I kinda prefer the centralized Windows registry to the "random assortment of config files" approach that Linux has. I think both Windows and Linux give you that feeling of carefully crawling around in ventilation ducts once you get your hands dirty; I doubt it's possible to get rid of that without getting rid of the inherent flexibility that the systems provide. There's a reason Windows has both the registry and the Settings app.
NixOS and Guix come close to this with a central spot for declaring the entire system state, including program configuration and env vars. Now there is still the $HOME/.config mess, which home-manager[0] tries to tackle.
From a typical user’s perspective, macOS puts all Preferences files into ~<username>/Library/Application Support/<app bundle name> or ~<username>/Library/Preferences/<app bundle name>, and they are standard Plist files readable by both command line and GUI tools that ship with the system, so easily editable and human-readable. From a power-user’s perspective, it is a Unix system and that part of it is the usual mess of Unix config files. I’m definitely a power user but rarely have any need to touch a Unix config file on my macOS systems.
This is also why I ditched Windows, about 15 year ago. But honestly, I get more ui freezes and beach balls today with Monterey than I do with Win 10. Windows has been getting better while MacOS has been slipping.
The multitasking on Windows is ridiculously bad.
Also, applications that freeze and can't be killed/restarted are simply part of life on Windows.
Add to all that, Window slows down over time - again, the periodic reformat and rebuild is part of life on Windows. After I switched to Mac I didn't need to rebuild the operating system essentially ever.
Also, the registry - I think the worst idea in all computing. Prior to the registry you plopped a windows application in a location and configured it with an INI file. After the registry the entire operating system and all applications turned into one big ball of chewing gum, glue and hair dredged out of the shower drain.
How can Windows have got it so wrong?