- Frameworks are more valuable to larger projects.

- Build your own framework and you know and control you code, inside and out. A lot of top devs will add to their own framework as they go.

- Where I disagree: PHP is not a framework, it’s an interpreted language.

People are way to agressive in some of their responses, they probably need to lay off the caffine, at least until they leave home. ;)

What? PHP is the only language I know where the helloworld app is just that: Hello world! This is because not even php programs don’t consider themselves programs but (html) documents. The closest thing in python are triple quoted strings, ruby uses heredocs AFAIK, however both denote strings and return strings. Php tags denote “not-a-string”, they don’t return strings, they suspend dumping to stdout. The core language includes a feature to interpolate variables (the analog to django’s {{foo}} form). php.net is predominantly full of documentation on building websites, that’s not true at all for python.org or ruby-lang.org, the standard library is full of web related functions, you’d have to compile php yourself to get rid of the headers_sent function for instance. If you command someone to install php, they’ll install apache + mod_php unless you instruct them otherwise. Yes you can ignore or exorcise the web related features and mostly ignore its templating nature and use it for crunching numbers, but that’s really an extra. PHP -as we know it- is a web framework, and there’s nothing wrong with that.

PHP is the no doubt the unsexy tow truck in this NASCAR race. But, when the others (Ruby, Python, blah, blah) are pushed to the curb for Next Year’s Hot Model, PHP will be hauling their carcasses to the recycling center.

I teach PHP, Ruby, and Python at CCSF and CSM. My prediction is that 5 years from now I’ll be teaching PHP and something else…Erlang? Haskell? oCaml? Joy? Who knows… But PHP will be on the schedule for sure. I guarantee it.

For more of the same, read this Sitepoint post about Rasmus’ take on “frameworks”.

You probably don’t understand the concept of framework if you call PHP a framework or try to suggest using a framework is not a good idea. Yes, one framework may be better for a certain job than other, othertimes native procedural PHP would be better (if you need speed). But, that certainly doesn’t mean PHP is a framework.

The problem with Twitter was not RoR but how they have used it. They could have ended up with same problem by using PHP. I like PHP, don’t use RoR, but we must be fair here. It was not the language the problem but how they implemented it. And their performance problem lied withing DB queries and DB structure not RoR itself.

I used CodeIgniter, Kohana, tried CakePHP and Symfony. CodeIgniter was best for what I did (I always liked speed). Now I am working on my own framework and CMS system.

You tried coming up with a cool title but in my opinion you have failed. The links in it ware useful though :)