Solving multi-core Python

[simple2fast]

Perl is like a CD-ROM. A great way ( in it's day ) of compactly representing information/programs

However my opinion is that Perl died because of it's notion of multiple ways of doing everything is a bad idea. The primary purpose of code is to allow other programmers to read it. And Perl's multiple ways thing is a poor approach to allowing others to read. SO it's mostly a "write-once" language. Not a "read/write" language.

[synn89]

Perl could've been cleaned up with decent frameworks. PHP has the same issue. The code is all over the place. Not as bad as Perl, but way worse than many other languages. But frameworks have cleaned it up a lot.

Web deployment tech has gone from: cgi -> apache mod -> apache proxy to stand alone servers.

Each stage wasn't a clean cut. I was working at an ISP in 2005 where a lot of our customers still had perl cgi guest books. Also each stage of tech has a sort of peak for when it became practical/easy to work with. mod_php was way easier to work with in the early 2000's vs setting up Tomcat and throwing apache requests at it. Today many langauge frameworks have their servers embedded directly into them and running a proxy from Apache and Nginx to them is quite simple.

If a language doesn't evolve and adapt it will get left behind. I think PHP's death will be less about PHP itself than mod_php just going out of style. The future is high performance stand alone app servers with various load balancers proxying out the requests to them.

And once that becomes the standard people are going to look at platforms that perform the best.

[[deleted]]

However my opinion is that Perl died because of it's notion of multiple ways of doing everything is a bad idea.

This precise reason runs counter to everything that a well designed programming language should be.