Linked by Thom Holwerda on Fri 10th Sep 2010 14:59 UTC
General Development Python programmers shouldn't get too smug. While many people agree that Python is designed in a way that makes it a highly readable language, there can still be problems with legacy, untested Python code too. Porting legacy Perl to Python can be a daunting task. In this article, learn some of the theory behind dealing with legacy code, including what not to do.
Thread beginning with comment 440760
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Why would I want to do it?
by reez on Mon 13th Sep 2010 12:59 UTC in reply to "RE[6]: Why would I want to do it?"
reez
Member since:
2006-06-28

I never really got the readability thing. I mean nobody says C is crap, because it isn't readable. It is damn hard to read and I am not only speaking about obfuscated code like this:
https://secure.wikimedia.org/wikipedia/en/wiki/The_International_Obf...

I always had liked Perls approach to make the programming language more like a natural language.

Also compared to similar languages other than Python I never got that argument. Ruby for example never suffered from the hard to read argument.

Of course there is some yucky Perl code, but to me it looks like this has more to do with it's age. Older code is harder to understand in most cases. The reason seems to be that the way people think about stuff changes over time. Today OO is overly hyped. Don't get me wrong, I like OO. In fact I am very picky about what OO really should look like. For example I don't really like the C++ style, but prefer Smalltalk, Objective-C and Ruby.

But be serious. OO is just one of many paradigms and there are always new approaches. So it is better to use external extensions like Moose to keep up with newer ways. Functional programming is an other big thing, but there isn't really one right way. Perl is pretty good when it comes to adopt new things. Every time the Python, Ruby, Whatever guys come up with something new I can be sure I will soon be able to use this in Perl.

I really like Ruby and Python, but every time I work on a project I get frustrated, because they show me their borders. The fact that neither of them have as many modules as Perl is also very frustrating. OO is all about code reuse, but it sucks when I always have to reinvent everything.

Maybe a project like Parrot could change this. They also have pretty nice support for a bunch of languages and got pretty far. They'd just need some publicity. It would be really nice if all the programming language projects would work together instead of having to reimplement the same stuff all on their own. Especially stuff like porting the platform somewhere else. That lack of support for a platform really sucks. It's also one of Perl strengths. It runs virtually everywhere. Again some advertisement, because I think this project is way too unknown.
http://parrot.org/

I guess I like the wrong stuff. Perl, Tcl, Smalltalk. All declared dead ;)

Reply Parent Score: 2

sorpigal Member since:
2005-11-02

Parrot will become increasingly known as perl6 becomes more complete. One way or another perl6 will be running on parrot and even though perl5 won't stop there are just so many advantages to perl6 that once I can get anywhere like enough performance out of it I don't see myself going back.

Parrot is like the open source answer to the CLR, though not advertised as such. It could be massively useful if its potential is reached.

Reply Parent Score: 2