News for hackers. Stuff that matters.
Re:Joe Stump: Why I switched from PHP to Python by sophacles on Friday September 04, 2009 @07:16PM (#805936)
Perl itself is not the problem. According to my friend, the problem comes from available tools: the ones he needs already exist for python but not for perl.

As for quick and dirty scripting in python: I do it all the time. Hell I just made a little "framework" [1] in python to do this better. I missed the while <> construct from perl for doing filters, so I made it easier to do in python. The funny thing is, many of my quick and dirty python scripts end up looking like more thought was put into them, and being more flexible, than they were ever intended to be.

[1] http://pypi.python.org/pypi?name=pyCLiFF&version=0.1&...

Re:Joe Stump: Why I switched from PHP to Python by zaphar on Friday September 04, 2009 @11:01PM (#806101)
Thats funny. I could say the same thing about the perl scripts I write. For that matter I could say the same thing The point is language and syntax for some of us at least has little bearing on how clear the code is. And like jrockway said perl is expressive enough that you can do far more abstraction in it. The only languages I've seen so far that can beat perl for expressive power are lisp and haskell.
Re:Joe Stump: Why I switched from PHP to Python by jamongkad on Friday September 04, 2009 @11:39PM (#806154)
As long as Python continues to not utilize multi-line lambdas. Then Perl and Ruby will continue to be a usable Lisp. But I don't think that's a bad thing. Python is Python and that's that.
Re:Joe Stump: Why I switched from PHP to Python by kingkongrevenge on Friday September 04, 2009 @10:09PM (#806068)
> the ones he needs already exist for python but not for perl

Rather unlikely.

Re:Joe Stump: Why I switched from PHP to Python by gaius on Saturday September 05, 2009 @03:38AM (#806318)
No really, hence the saying "only Perl can parse Perl". Despite its dynamic typing, Python is quite amenable to tool support because of its regularity.