← Back to context

Comment by manwe150

1 day ago

The difference is Linux has fork, while Windows doesn’t, so Linux cannot do accurate accounting (without wasting a lot of memory) while Windows can.

macOS is a UNIX as well, and it isn't the only UNIX that manages to do accounting properly.

  • macOS includes a GUI user land whereas Linux is just a kernel.

    So Apple can build a whole user-controlled GUI workflow around memory exceptions, which Linux cannot.

    Maybe what needs to happen is new Linux syscalls + signals for DEs to utilise for building memory exception UIs? But the problem then with that is you’re impacting the portability of those DEs. So some maintainers might still refuse to work with Linux to provide this.

    That all said, I’m pretty sure KDE does provide GUI tools for when this kind of scenario arises.

    • I mentioned they aren't the only UNIX where this isn't a problem.

      Also we cannot use the reasoning Linux means distributions, instead of using GNU/Linux for it, and other times Linux is just the kernel, depending on convenience.

      3 replies →