[nickrio]

You just notice "Old"? Old usually are not cause any problem, but when you combine old and narrow, that is not a good thing.

It just like Morse Code which designed for telegram operators to send and receive message.

By that time when telegram was new, it was a good invention, everyone who wants to use telegram must know Morse Code. And because of it's designed for telegram, it come with every each bonus to make send and receive telegram faster.

However, one day, a new technology been invented, it's called Telephone. Not long after that, telegram started to fade away.

What fade away with it, is of course, the Morse Code. Because it only good at sending and receiving telegrams which not many people still do today.

Now the PHP. It has a lot of old burdens (To make it good at outputting HTTP respond) and poor design decisions. They need to find a way to organize those things and carefully redesign that language. Then, maybe it can become respectable.

[dvfjsdhgfv]

It's almost the opposite of what you're saying. As PHP was designed for web development, "newer" languages often need a lot more (configuration, modules, etc.) to produce what PHP can easily do by default.

[stephenr]

Your analogy doesn't work.

We haven't moved on from http for web applications.