12 Jun
2010
12 Jun
'10
6:13 p.m.
Unless you are using a framework like Twisted, where all potentially blocking operations are handled by passing in a function to be called when the operation is complete, so that the stack trace is non-existent. This way you get both the joy of working with a language where simple mistakes won't be caught automatically until they cause a failure at runtime *and* the joy of not having traces that tell you exactly what led up to an error. Fun times. Not that I'm bitter... :-) Cheers, Greg On Jun 12, 2010, at 2:50 PM, Marc Weber wrote:
Ruby, Java, PHP, Python.. may win here because you have stack traces. However I bet errors are much more likely to happen