Hacker News Reader

slackingoff2017

Events and asynchronous operations are sufficient enough for a concurrency library to be built on top of JS with minimal changes. I wouldn't consider what JS has now a reasonable concurrency model but the asynchronous event handling could serve as a starting point for a source of events that run on multiple threads.

View on HN

That was the state-of-the-art in OS concurrency in the early nineties. Sometimes, you would have to reboot your computer because some app forgot to yield the event loop.

It's not as bad if you have to restart your app because some task forgot to yield the event loop, but it's still bad.

Threads solve this problem comprehensively because threads get to make progress regardless of whether or not other threads are in a loop.

> That was the state-of-the-art in OS concurrency in the early nineties.

Many systems had pre-emptive multitasking in seventies and eighties.

I think Amiga was the first implementation for consumers. Released in 1985. https://en.wikipedia.org/wiki/Amiga_1000

Reply on news.ycombinator.com