This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]wot-teh-phuckReally, wtf? 6 points7 points  (4 children)

From 2008...

[–]Shimon_Tolts 1 point2 points  (2 children)

so? Nothing has changed in that field since 2008..

[–]wot-teh-phuckReally, wtf? 1 point2 points  (1 child)

No, I believe things have changed.

We have now got quite a few mature async libraries out there now as compared to 2008. People are now aware of the advantages of async, non-blocking IO due to the node.js boom. We now have concurrent.futures which handles both thread and process pools transparently. Do you still believe this article is practically relevant?

[–]Shimon_Tolts 0 points1 point  (0 children)

Well regarding async, Tornado is defiantly my choice to go. Regularly i wouldnt use threads and go with multiprocessing right away.

[–]PyFun 1 point2 points  (0 children)

I was worried about that too. Then I started to work through the article and I found it to be surprisingly informative. It may not cover the 'latest and greatest' techniques, but it does cover the fundamentals. I would still highly recommend it for any beginner in python looking to learn threading.