News for hackers. Stuff that matters.

A comment on Threads Are a Bad Idea for Most Purposes (1995) [pdf]. Parent comment

Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by oppositelock on Tuesday January 28, 2020 @02:56PM (#22173428)
You can write horrible event driven code. For example, do your events need to talk to a database? Right there, you've got a synchronization point.

Thinking about asynchronous behavior is always tricky, and code designed to run on threaded systems isn't generally arbitrary code with locks thrown into it the mix, you strive to write the largest possible reentrant sections, and only lock where you have to, and as infrequently as possible. With reentrant code, it doesn't matter where you get preempted.

[ Parent | on HN ]
Re:Threads Are a Bad Idea for Most Purposes (1995) [pdf] by lmm on Tuesday January 28, 2020 @09:26PM (#22176606)
> For example, do your events need to talk to a database? Right there, you've got a synchronization point.

Not if you do it right. Interacting with sync-only systems from async systems is a problem, but it's not fair to blame that on async - if you make the whole system work async, you don't have that problem.

[ Parent | on HN ]