Live data from Hacker News

Why PHP continues to thrive in the age of the PaaS

plus.google.com

81–90 of 102 posts

Re: Why PHP continues to thrive in the age of the PaaS

#81
post #32

PHP is popular because of it's simplicity, low cost (like zero) of entry and because of Wordpress. But the pay rate for PHP developers is miniscule because every Pakistani and Indian is a PHP expert for $1/hr. Try to post a $20 professional website job on Elancer - and in 10 minutes you'll get 20 lancers eating each other for your "business". So "thriving" is to be taken with a grain of salt.

You're forgetting Drupal.

Re: Why PHP continues to thrive in the age of the PaaS

#82
I think this is a fallacy. Easy deployment has nothing to do with why PHP is still this popular; I think it has a lot more to do with PHP being beginner-friendly, in that when things break, they always semi-work as opposed to leaving the wannabe developer completely lost.

For the sake of comparing, here's how I make a throwaway app super quickly in Ruby, almost equivalently to a PHP deploy:

    $ ssh server
    $ kenji init project # [1]
    $ cd project
    $ tmux # launch a background session, edit some code
    $ bundle exec rackup # in a pane next to my code
Boom, brand new web-app is running on my server in less than a minute's work.

[1]: This is a Ruby web-app microframework. https://github.com/kballenegger/kenji

Re: Why PHP continues to thrive in the age of the PaaS

#83
post #23

Earlier quoted context omitted.

The problem is learning PHP actually makes you worse at PHP. The only possible way to program PHP is to be pretty much ignorant of everything in which case PHP will actually do kinda what you wanted. If you learned PHP then either it's not actually doing what you think it's doing, or some config variable changed and would have done what you thought except it didn't, but don't worry just add some code to change that c…

Thank you dearly for this. What's your opinion on SSI?

I'm not personally a huge fan of SSI, however, it's simple and understandable, and things do what you think they do.

What I like about it is clean separation, a few command for common things, and if SSI doesn't directly support what you want you just hand it off to another program.

Re: Why PHP continues to thrive in the age of the PaaS

#84
post #58
post #24

Earlier quoted context omitted.

> You're making the mistake of conflating PHP the language with Rails the Framework. I've heard someone call PHP "the C web framework". I thought it was fitting, and in addition, it seemed that even as a C web framework, it was a failure.

PHP may have some rather serious flaws but it is far from a failure and runs on a huge majority of the web.

Agree that it has flaws, agree that it not a failure, but what do you mean "runs on a large majority of the web"?

Re: Why PHP continues to thrive in the age of the PaaS

#85

Earlier quoted context omitted.

You're making the mistake of conflating PHP the language with Rails the Framework. I can do your app in Rails pretty damn quickly at this point (with one of my current skeleton frameworks I can add authentication administration and other nice features pretty much "for free" as well) But tell me I have to do it CodeIgniter or Laravel and I'd be completely lost for days.

The question then is, can you throw together a website in Ruby? Plus, have your non-technical folks be able to edit the templates?

By the time your "non-technical folks" are editing templates, you have a problem regardless of your language/framework. If you only have enough knowledge to "add an image" stay out of my HTML!

Re: Why PHP continues to thrive in the age of the PaaS

#86

Because the vast majority of PHP programmers began their programming journey by trying to post from a form built with static html, and worked their way down. In my experience (YMMV), they tend to lack the general programming concepts and practices that programmers who come from a CS/general computing (instead of web design) background are more likely to have, making it more difficult for the PHP programmer to move in…

I have a bone to pick with your last contention. At what load does the PHP runtime begin to become the performance bottleneck, particularly with APC enabled? As far as I know, Facebook is about the only application with enough load to test the limits of the PHP interpreter itself. I was under the impression that PHP itself is actually quite performant...

Facebook runs compiled/JITted PHP code.

Re: Why PHP continues to thrive in the age of the PaaS

#87
post #85

Earlier quoted context omitted.

The question then is, can you throw together a website in Ruby? Plus, have your non-technical folks be able to edit the templates?

By the time your "non-technical folks" are editing templates, you have a problem regardless of your language/framework. If you only have enough knowledge to "add an image" stay out of my HTML!

my life got so much easier when i stopped pretending that non-programmers should be able to work on the templating layer.

Re: Why PHP continues to thrive in the age of the PaaS

#88

Earlier quoted context omitted.

I know the author emphasizing a point, but the steps that he's described end with two vastly different results: 1 - A php script on a server with a script with some code on it. vs 2 - A full featured MVC framework, complete with version control, database integration, easy deployment, which is easy for other developer to jump into, etc etc How can these two options be equated?

A lot (a majority?) of websites aren't made by people that need those things. A lot of people just want to get their ideas up on a page so they can show their friends. The thing I walked away with from the article was that PHP is still active in part because it has such a low entry point for those people, where as Rails does not. Like you said, they're very different entities, but a lot of people can't tell or don't…

i'm personally learning to love static html again. the longer i can get away without a users database the better.

Re: Why PHP continues to thrive in the age of the PaaS

#89

Because the vast majority of PHP programmers began their programming journey by trying to post from a form built with static html, and worked their way down. In my experience (YMMV), they tend to lack the general programming concepts and practices that programmers who come from a CS/general computing (instead of web design) background are more likely to have, making it more difficult for the PHP programmer to move in…

I have a bone to pick with your last contention. At what load does the PHP runtime begin to become the performance bottleneck, particularly with APC enabled? As far as I know, Facebook is about the only application with enough load to test the limits of the PHP interpreter itself. I was under the impression that PHP itself is actually quite performant...

see: drupal.

having to execute the whole application from the entry point on every page hit is just awful. APC will only save you the loading from the disk and compiling part, not the whole execution chain.

with node and others the application is just sitting there, listening to a port, and fires the right callbacks when a request comes in. the application startup cost is paid once. not on every request.

there are people who have tried to reproduce it in php by having php running and serving multiple requests in a similar manner. This is really treacherous since php didn't even pretend to free memory under any circumstances ever, until about php 5.3.

since moving over to writing servers, i just feel that the php model of executing the script when a url is hit is just fundamentally wrong.

Re: Why PHP continues to thrive in the age of the PaaS

#90
post #32

PHP is popular because of it's simplicity, low cost (like zero) of entry and because of Wordpress. But the pay rate for PHP developers is miniscule because every Pakistani and Indian is a PHP expert for $1/hr. Try to post a $20 professional website job on Elancer - and in 10 minutes you'll get 20 lancers eating each other for your "business". So "thriving" is to be taken with a grain of salt.

Well you want to avoid those freelance sites anyway regardless if you're doing projects using php or not. Making a good living building stuff is not even about what language you use, it's all about networking and how good you're talking with clients.
Post reply on HN