4 ms·
It's because you're thinking "it does X! it's not ambiguous!" but still missing that the question is over why it SHOULD do X instead of Y, not over whether it d
by dataflow 6y ago
It's because you're thinking "it does X! it's not ambiguous!" but still missing that the question is over why it SHOULD do X instead of Y, not over whether it does X or Y. To a user, it sure as heck doesn't make sense to fork a process and still end up with one window for both of them. For lots of processes the process is its windows as far as the user is concerned.
- deleted 6y ago[deleted]
- robotresearcher 6y agoFork isn't an idea that users need to have. Devs may need to know what their OS API's fork() does. No-one else cares.
- dataflow 6y agoThat's an argument for "I don't care about this", not an argument for "this abstraction is sensible".
- megous 6y agoUsers don't fork processes, it's a low-level system thing.
- dataflow 6y agoWhy repeat the same thing as the sibling comment posted an hour ago...?
- CRConrad 5y agoUsually because you've had the browser open for a while and are seeing the state after the parent, but before the sibling comment was posted. At least that's usually why it happens for me; refreshing to see if someone else already has said what you want to say is rarely uppermost in my mind when a reply comes to mind. Another possibility (pretty clearly not the case here) is when there are lots of replies: either you just miss it among the others, or ypu just can't be bothered to scroll down half a mile.