That was implied in the post you were originally refering to (#26).

In fact, that is always implied when using any GNU/Linux.

But what use is that to a newbie who has a "Question before moving to Linux/Ubuntu"... when their hard drive starts spinning ceaselessly or suddenly things mysteriously break although they "didn't touch it". Rhetorical question, no need to answer.

Yes, but there is a big difference between being able to switch it off and not, particularly in the context of this discussion. Windows updates used to be automatic by default, but they could be switched off: the issue the OP has is that with Windows 10 they can only be postponed for a short period of time.

On balance, it's more useful than a situation where to receive critical security patches or bug fixes the newbie needs to open a terminal emulator and start typing in commands. There is always some degree of learning curve with anything, but I'm confident a newbie (perhaps with the help of a web search) will manage their way around an update program with a GUI and adjust their update settings if they find them a nuisance.

Here's an interesting psychological observation:
I installed Mint on the first laptop I bought because I wanted to ensure that the wifi worked. It was a Broadcom chip and that needs some firmware called (I think) b43, which Mint supplies. I don't remember the release, but it was a lot more traditional than recent Mint releases.

There were two package managers. One was synaptic and the other was a newbie-friendly update manager, which would buzz you if there were updates available. It classified updates according to their ability to damage the system. For example a kernel or bootloader upgrade was Grade 5. By default, only updates up to grade 3 were carried out. If you wanted to do a more dangerous update, you had to override a warning.

I never did that! I knew it was irrational, because if I had been using synaptic, I would have updated these things along with everything else. After all, kernel patches are usually to fix security holes. But being told, "This is dangerous" paralysed me. I never did update the kernel on that machine.