5 ms·
> For historical reasons, that area where almost everything executes is called “userspace.” It's an old term at this point, but I don't think the reasons for i
by Retr0id 2y ago
> For historical reasons, that area where almost everything executes is called “userspace.”
It's an old term at this point, but I don't think the reasons for it being called "userspace" have changed or become outdated since then, so I wouldn't call them historic per se.
- deleted 2y ago[deleted]
- Macha 2y agoThings have gotten messier with virtualization, containerisation, hypervisors etc. The internet loves to produce pedants to argue the post should go into the finer points of these even when it's not relevant to the message. And so people like the author have a defensive reflex to throw in some language to bounce the pedants away.
- SoftTalker 2y agoI used to like Patrick's posts but lately they are way to long and full of irrelevant minutia. Decide who you're writing for, and write to that audience.
- rescbr 2y agoSome of his audience likes the irrelevant minutia.
- rozenmd 2y ago> Decide who you're writing for, and write to that audience. He has, and he does.
- arduanika 2y agoCongrats, you've been screenshotted and tweeted by him! "In which an HN commenter offers me writing advice but fails to understand the implication of second sentence" https://x.com/patio11/status/1818757982706139297 https://x.com/patio11/status/1818757982706139297
- shadowgovt 2y agoWhy is it called "userspace" when all it runs is some Docker containers hosting a web frontend's server, and no human being ever telnets into it? Where's the "user" in that story? Where is the "user" when the machine is a Windows box stuffed behind a façade wall that displays airport directions, notifications, and ads on rotate?
- anticristi 2y agoI always understood "user" in "userspace" as "the user of the operating system kernel".