> An unprivileged userspace application, even if coded poorly, shouldn't crash the machine.
How would you prevent that? It can write until root disk is full, can take all your memory, saturate your CPU and a whole bunch of other stuff we (users) like to be able to do for the things that need them.
Unless you're suggesting something like Qubes or similar UX?
Right, my point being that it's should be up to the user to decide, because most of the times I run programs, I actually want them to be able to gobble up GB of disk, RAM and fully make use of my CPU. That's why I bought the hardware I have :)
Isn't that the default? The user has access to all available memory unless they (or an admin) set a restriction. Unavailable memory is only unavailable because writing to it crashes the kernel, thus preventing you from using your hardware!
Yes, it is, and for good reasons. That's why I disagreed with the original "An unprivileged userspace application, even if coded poorly, shouldn't crash the machine" part.
I don't follow. The default today is that an unprivileged user space application should not crash the machine. The kernel reserves what it needs, then hands the rest to user space. Thus, all available memory should not crash the machine.
I don't think you can put this on Zed. An unprivileged userspace application, even if coded poorly, shouldn't crash the machine.