[Fixed] Forced to install Windows 10?

[Mr. Scram]

Fusion Drive for mixed HDD/SSD systems, and Retina Display for high-DPI monitors.

Fusion Drive allows you to use the space of the sum of SSD and HDD in the system. The kernel will move hot data in the SSD while move cold data into HDD as needed.

Retina Display scales display elements to match the DPI of the monitor on a much lower level than most other OS, resulting a much prettier HiDPI user interface.

Also, macOS is a fork of BSD. Being UNIX its kernel is much more reliable than Windows. My installations of macOS reboots only when a kernel update ir a hardware modification is in order. It is my daily driver. It can still record uptime of months even under constant interactive use.

I think Intel offers the same. You can add an SSD and the system will work out what files are used most.

I'm not sure about the kernels. I see plenty of Windows Servers with uptimes measured in months. That has been same kernel as the desktop stuff for a while now. Besides, uptime isn't as cool as it used to be. Timely patching is.

[cdev]

Or better yet, run open-source Linux without systemd and with a low overhead display manager.

Your machine will run much faster and you'll get more work done.

[bd139]

So FreeBSD with i3 

Actually now I look back at what I’ve written it’s not such a bad idea.

(Not a fan of systemd or much of the Linux boot process)

[Mr. Scram]

Or better yet, run open-source Linux without systemd and with a low overhead display manager.

Your machine will run much faster and you'll get more work done.

I literally won't get any work done, due to specific constraints. Horses for courses.

[technix]

Fusion Drive for mixed HDD/SSD systems, and Retina Display for high-DPI monitors.

Fusion Drive allows you to use the space of the sum of SSD and HDD in the system. The kernel will move hot data in the SSD while move cold data into HDD as needed.

Retina Display scales display elements to match the DPI of the monitor on a much lower level than most other OS, resulting a much prettier HiDPI user interface.

Also, macOS is a fork of BSD. Being UNIX its kernel is much more reliable than Windows. My installations of macOS reboots only when a kernel update ir a hardware modification is in order. It is my daily driver. It can still record uptime of months even under constant interactive use.

I think Intel offers the same. You can add an SSD and the system will work out what files are used most.

I'm not sure about the kernels. I see plenty of Windows Servers with uptimes measured in months. That has been same kernel as the desktop stuff for a while now. Besides, uptime isn't as cool as it used to be. Timely patching is.

I have been bitten by Intel’s offerings. It had a 64GB SSD cap, the useable space is equal to that of the HDD, and it is fragile AF.

Linux’s bcache is a lot better without the SSD capacity cap and is adequately robust. Although you still lose the SSD space in total useable storage.

Windows 10 now forces reboots. Somehow in Windows almost all system update requires a reboot. On both macOS and Linux unless the kernel or init is being touched no reboot is needed whatsoever.

[bd139]

My Mac goes into a coma and the WDT fires if I shut the lid about 1 in 10 times. You win some and lose some.  It merely takes the title of least painful desktop and least likely to fuck up hardware.

The only truly reliable machines I have under my command are HP DL series with CentOS and they don’t have a desktop. They literally never do anything untoward. Even when some turdblossom wrote a java fork bomb by accident when parallelising an operation and managed to create a few tens of thousands of threads across 50 nodes, nope hardly even noticed it.

[Mr. Scram]

I have been bitten by Intel’s offerings. It had a 64GB SSD cap, the useable space is equal to that of the HDD, and it is fragile AF.

Linux’s bcache is a lot better without the SSD capacity cap and is adequately robust. Although you still lose the SSD space in total useable storage.

Windows 10 now forces reboots. Somehow in Windows almost all system update requires a reboot. On both macOS and Linux unless the kernel or init is being touched no reboot is needed whatsoever.

Again, uptime isn't as cool as it used to be.

[bd139]

Very true. Uptime is nothing to be proud of and never was. Patched up kit that can handle multiple node outages is something to be proud of. If it’s a desktop machine, who cares as long as it’s patched.

[rdl]

It's just an annoyance, but I don't get bothered by it much anymore. I only let it update when it's convenient for me. I don't have the service running constantly, just start it up once a month to get the security rollup then shut it down till next time.

[grumpydoc]

Very true. Uptime is nothing to be proud of and never was. Patched up kit that can handle multiple node outages is something to be proud of. If it’s a desktop machine, who cares as long as it’s patched.

It's not so much the uptime (as you say, not really an issue on a desktop system), but the inconvenience.

I am the sort of person who can quite easily find myself bashing out an essay (or bit of software) in an all nighter just before the deadline - yes, yes, I know - but a forced update and couple of reboots in when I am already stressed is not good!

[technix]

Very true. Uptime is nothing to be proud of and never was. Patched up kit that can handle multiple node outages is something to be proud of. If it’s a desktop machine, who cares as long as it’s patched.

It's not so much the uptime (as you say, not really an issue on a desktop system), but the inconvenience.

I am the sort of person who can quite easily find myself bashing out an essay (or bit of software) in an all nighter just before the deadline - yes, yes, I know - but a forced update and couple of reboots in when I am already stressed is not good!

This is the thing macOS and Linux does NOT do. It will not force install any updates. macOS will be naggy once a day but you can safely discard it.

[Mr. Scram]

This is the thing macOS and Linux does NOT do. It will not force install any updates. macOS will be naggy once a day but you can safely discard it.

I've never had Windows reboot on me if I didn't tell it that I could. It seems mostly to be a matter of PEBCAK.

[grumpydoc]

This is the thing macOS and Linux does NOT do. It will not force install any updates. macOS will be naggy once a day but you can safely discard it.

I've never had Windows reboot on me if I didn't tell it that I could. It seems mostly to be a matter of PEBCAK.

Windows 10 will.

[Mr. Scram]

Windows 10 will.

It hasn't so far, with plenty of miles on the clock Sometimes it needs some tough love, but few OSs don't.

Note that I'm not denying Windows 10 and the attempts to upgrade people to it haven't been intrusive. They absolutely have and it was dreadful behaviour on Microsoft's part.

[grumpydoc]

Windows 10 will.

It hasn't so far, with plenty of miles on the clock Sometimes it needs some tough love, but few OSs don't.

Note that I'm not denying Windows 10 and the attempts to upgrade people to it haven't been intrusive. They absolutely have and it was dreadful behaviour on Microsoft's part.

Maybe they tamed that with the latest update but before then I remember at least two occasions my laptop forcibly rebooted. there was a countdown timer and a bit of notice but no way that I could see to prevent it happening.

I rarely use that laptop (as it does not live in my main residence) so it probably had a whole bunch of updates at the same time.

[bd139]

It always goes off when you've got three VMs running and 11 copies of Visual Studio open and just literally reproduced that shitty bug after three days of config hunting and crawling through no documentation.

[technix]

This is the thing macOS and Linux does NOT do. It will not force install any updates. macOS will be naggy once a day but you can safely discard it.

I've never had Windows reboot on me if I didn't tell it that I could. It seems mostly to be a matter of PEBCAK.

Way too many times had Windows gave me the 30 second countdown towards update reboot when I was knee deep in Eclipse or Atmel Studio banging out code. That thing is intrusive AF and I usually lose track of things when it comes back up.

Annoying even more when I tried to reproduce an electrically-induced code bug when this pops up. To trigger the bug itself requires some Goldilocks condition that takes a lot of tries. Breaking the flow here will render me unable to fix the bug.