Hacker News new | past | comments | ask | show | jobs | submit login

Every one I know of has regretted it, and seen it as an antipattern. For example, Java way back in 1.5: http://docs.oracle.com/javase/1.5.0/docs/guide/misc/threadPr...

I think Erlang might be okay with it, because "this thread can fail at any time" is a core value of Erlang. But it's an exception.




Haskell has killThread, which rather than being an anti-pattern is often used as an effective way to accurately enforce a timeout on a thread. This functionality seems like it would be very difficult to achieve with most other runtimes. https://news.ycombinator.com/item?id=11370004


You have a sibling comment elsewhere in the thread which disagrees; I'll leave that argument to that sub-thread.




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

Search: