Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

(I was going to opt out of this, but I can spend another 1/2 hour on it_).

What you are saying is, you're a client of someone else's nonblocking event loop. So all the classical stuff regarding nonblock io loops apply.

E.g: http://talkingcode.co.uk/2008/12/02/haskell-gtk-and-multi-th...

But substitute Gtk for Qt, or anything where you're the sucker dealing with an external concurrency model or event loop.

Hilariously, they end up having the same debate we are here, just in Haskell.

Seriously, there's no pixie dust for this.



That link is a good example of exactly why we need to push for languages to take concurrency seriously. That's an example of how a haskell user has to deal with the issue when interfacing with a C lib that rolled their own event loop. For most languages people have to deal with that issue all the time, for their own code, entirely in that one language.

I have no idea why you are talking about pixie dust. My point was that explicitly using event loops instead of abstracting it into a green thread library is dumb, and we need to start having higher expectations from languages rather than accepting backwards shit like node. Not "green threads are magic".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: