Thermopyle posted:

• Python has threading/multiprocessing.
  
• Python is better suited to avoiding the callback hell of JS/Node.
  
• The norm in Python land is for libraries and the standard library to be well-tested and used in the wild for a long time.
  

Thermopyle posted:

Hah!

I knew exactly who would post this.

Tao Jones posted:

With Node, I often feel like I have no earthly idea in advance what a function is going to be returning. Is it going to be a promise? Is it going to be an object that isn't a promise? A string? Undefined because something got hosed up?

Similarly, I find I'm often in situations where if I try to deviate slightly from a provided example -- ie, in the tutorial everything is just mashed into one large function but in my code I want to break each piece into smaller functions -- I particularly hit this snag where async fucks things up or there's some weird promise interaction or something.

Is there any kind of cheat sheet or quick and dirty guide to where some common minefields are, or is this just the kind of stuff I just have to bang my head against?

dbcooper posted: