Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Fun fact: because the browser tab runs on an event loop, ^W is actually polled, although not directly - it's resolved into an event object in a queue which is then polled.
Although I suppose the task queue supports both polled and signal based operation, when the queue is empty the page goes to sleep and when the first element is pushed the queue wakes it up.
c3r38r170336139dThis is probably a Joke/Meme, but it's a story so I'll allow it. Plus me caés bien.
I am not sure you're right.
But the browser if finding meaning in closing the tab. So it just closes the tab.
The browser itself shouldn't be running on an event loop. It knows true concurrency. I mean, there was a time in which browsers tried to be faster by opening multiple parallel sockets and those must be handled in threats.
I know very little about how any browser is built, but I do not see why they would go back to event loops when they are in a language with threats.
I mean I could imagine that there is an equivalent of kill -9 for tabs. Then you would be right.