giusc

Coincidently, downloading anything from wi-fi or cellular network is exactly the same thing. Just on steroids.

Most common symptoms of PFO are described in the article: "migraine headaches, or have altitude sickness at 5,000 feet instead of 10,000 feet, or find yourself panting while doing a slow jog, no matter how often you train." Also should be noted that there are much many other subtle syndromes that can lead to sudden cardiac death, many are detected accidentally when testing something else (going to the ER because of a car accident) There's no math formula to detect how and when each of us will die one day.

Look at the php.net website source code. Another example could be the Wordpress source code. It's not handsome code, but it just works.

Things like fat (either slim) frameworks should be memory resident (java or similar), not reloaded from scratch at each web request, it just won't never perform on big sites. Alternatively, if you need to deal with bigger applications, or massive traffic, you can build some kind of backend memory resident application (c, c++, java, go...) and delegate the hard work to it by using a lightweight rpc protocol (see messagepack, thrift, protobuf), and leave PHP alone to do the job it's born for.

Also, the choice to adopt a framework is serious stuff, it firstly should be well designed and maintained, then it should suit exactly your needs and more importantly you should not just use it, but learn conventions and write your code by sticking on them or else all your code will result in a bad mess.

My personal opinion is that either no symfony and no pux should exist.

There's no need to reinvent frameworks in PHP as PHP is the framework already. There's no need to reinvent templating in PHP as PHP is the templating already.

If you require different productivity from a language just don't stick on PHP and make the right choice by using the most appropriate language for you. There's plenty out there.

PHP is great, it rocks and is very fast when used in the right way.

Sounds to me like the classic apples and oranges comparison.

In my opinion Javascript's evolution has become a requirement more than just a story of success. It was the de facto standard language for browsers but with big lacks of performances. Browsers vendors worked to improve it and everything was only a natural consequence of the evolution of the World Wide Web.

Perl's history is completely different. Perl has always worked behind the scenes, and still does it greatly. It has a stable, rock solid, very performant and widely spread runtime.

Let's just call things with their names and use them for the purpose they are born and everything will look less confusing.

More than else, always remember: You can write FORTRAN in any Language.