tag:blogger.com,1999:blog-4622775563416752930.post4629258589859599202..comments2022-09-01T20:53:27.194+01:00Comments on Mark's stream of verbiage: Why I use PythonMark Robsonhttp://www.blogger.com/profile/15864507044869250062noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4622775563416752930.post-63700654114422784732015-03-30T21:55:06.663+01:002015-03-30T21:55:06.663+01:00I'd also choose Python over Perl any day. The ...I'd also choose Python over Perl any day. The "many ways of achieving the same goal" of Perl just does not sit well with me. Also, Python nicely combines some functional elements, such as lazy sequences and co-routines, with imperative languages.<br />However, I still think that people choose scripted languages too often - where speed matters, I'd still take C++ or Java.<br />Roman Kleinerhttps://www.blogger.com/profile/03917767413473119617noreply@blogger.comtag:blogger.com,1999:blog-4622775563416752930.post-88402162035618763992015-03-29T08:04:48.687+01:002015-03-29T08:04:48.687+01:00I also would prefer Python to Perl any time of day...I also would prefer Python to Perl any time of day. It's not so much the stack traces (they are not easy to get in asynch Python either), but readability, co-routines, and balance of functional and imperative language.<br />But, coming from C++ background I still can't get used to how little help the running environment provides. You can write an utter garbage in an error handler, and the language just swallows it. This is of course common to all scripted languages.Roman Kleinerhttps://www.blogger.com/profile/03917767413473119617noreply@blogger.com