11–20 of 349 posts
But what's the point? The beauty of perl scripts, and later php templates, was in their BASIC-like simplicity. They were not secure or structured in any way, but very accessible. Once you add these frameworks, you realize you could have started with Python or Java in the first place and get more mature infrastructure and better language along the way.
But what's the point? The beauty of perl scripts, and later php templates, was in their BASIC-like simplicity. They were not secure or structured in any way, but very accessible. Once you add these frameworks, you realize you could have started with Python or Java in the first place and get more mature infrastructure and better language along the way.
In the mid-00s the main selling point of PHP were shared hostings with mod_php which was a cheap way to host your own web site and database. Now with the cloud that advantage is utterly gone.
Earlier quoted context omitted.
Yet this internet myth of "PHP no bueno" persists. Don't confuse the tool with the artisan. PHP is an incredible language that's getting more mature with each new release.
Why do PHP developers insist on calling themselves artisans? Give me a call when PHP ditches backwards compatibility and cleans out all the shit from the standard library - 5845 global functions always available, most of which you are just supposed to know are shit... Just a nightmare.
But what's the point? The beauty of perl scripts, and later php templates, was in their BASIC-like simplicity. They were not secure or structured in any way, but very accessible. Once you add these frameworks, you realize you could have started with Python or Java in the first place and get more mature infrastructure and better language along the way.
In the mid-00s the main selling point of PHP were shared hostings with mod_php which was a cheap way to host your own web site and database. Now with the cloud that advantage is utterly gone.
I have the same access to my shared hosting, and the amount of money per year is peanuts.
But what's the point? The beauty of perl scripts, and later php templates, was in their BASIC-like simplicity. They were not secure or structured in any way, but very accessible. Once you add these frameworks, you realize you could have started with Python or Java in the first place and get more mature infrastructure and better language along the way.
In the mid-00s the main selling point of PHP were shared hostings with mod_php which was a cheap way to host your own web site and database. Now with the cloud that advantage is utterly gone.
With the advent of Chinese frameworks that solve C1000K problems like swoole, workerman and so on it even found its place as high performance interactive backend server.
Earlier quoted context omitted.
Why do PHP developers insist on calling themselves artisans? Give me a call when PHP ditches backwards compatibility and cleans out all the shit from the standard library - 5845 global functions always available, most of which you are just supposed to know are shit... Just a nightmare.
Artisans? First time I hear that. I certainly use PHP and never called myself an Artisan.
Earlier quoted context omitted.
Yet this internet myth of "PHP no bueno" persists. Don't confuse the tool with the artisan. PHP is an incredible language that's getting more mature with each new release.
Why do PHP developers insist on calling themselves artisans? Give me a call when PHP ditches backwards compatibility and cleans out all the shit from the standard library - 5845 global functions always available, most of which you are just supposed to know are shit... Just a nightmare.
But what's the point? The beauty of perl scripts, and later php templates, was in their BASIC-like simplicity. They were not secure or structured in any way, but very accessible. Once you add these frameworks, you realize you could have started with Python or Java in the first place and get more mature infrastructure and better language along the way.
PHP share-nothing architecture is awesome. It's amazingly simple and it scales to arbitrary size.
At which point there’s little difference from .
Earlier quoted context omitted.
Yet this internet myth of "PHP no bueno" persists. Don't confuse the tool with the artisan. PHP is an incredible language that's getting more mature with each new release.
Why do PHP developers insist on calling themselves artisans? Give me a call when PHP ditches backwards compatibility and cleans out all the shit from the standard library - 5845 global functions always available, most of which you are just supposed to know are shit... Just a nightmare.
In other languages, you can import code like this:
import mail as mailer
In PHP, it is the other way round. Every piece of code needs to try avoiding namespace conflicts by prefixing the code with something like this:
namespace Illuminate\Mail;