more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
"I shudder at the thought of having to learn Parseltongue..." If you've been coding Perl for any length oftime and have a reasonable understanding of OO, Python is exceptionally easy to grasp, particularly in the case you mention that most of your peers use it for simple things. Here's a pretty decent intro. One problem with Python I've found at work, is sometimes people go way too crazy with significantly ridiculous levels of inheritance that oftentimes don't even have a proper hierarchy (think 10 levels with cross-pollution). I suppose that happens in Perl as well, I've just never seen it. I feel that it's handy to at least have some working knowledge of languages that are widespread, even if only for a single reason: porting a library or portion of code to Perl ;) For the Rasperry Pi work I've been doing lately, oftentimes I refer to existing Python code when I'm writing a new module for specific devices/sensors etc. I read the datasheet, harvest and/or write C code, the review the Python of known good existing libraries as a comparison to how I'm thinking I want my API to work. Python is king in the Pi world (well, C is really, but the majority just want it "easy" so they use RPi.GPIO), so understanding Python has made it a bit easier for me to help provide Perl users the same benefits that the Python kiddies already have. In reply to Re^2: Perl vs Python revisited
by stevieb
|
|