"The platforms that win on the web are those that mirror its fundamental structure, not those that try to morph it into a more traditional "elegant" shape." This reminds me of why C succeeded, because it mirrors Unix so well, that C and Unix succeeded hand in hand. So this part about PHP mirroring the shape of the web made the most sense to me, as someone who doesn't know any PHP.
>C succeeded, because it mirrors Unix so well Actually, Unix succeeded after it was rewritten in C. (Not counting the very first Unix version which was done in assembler. See http://www.livinginternet.com/i/iw_unix_c.htm )
Why PHP won
31–40 of 61 posts
Re: Why PHP won
#32This article is totally barking up the wrong tree. PHP's growth had little to do with its appeal to programmers, and lots to do with its appeal to shared hosting providers. Safe mode is what I'm talking about.
It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life.
I really love Linux, Apache and MySql. So doing things in LAMP is just great for me.
Hosting is a big part of my business, so yeah - its cool that PHP is all around. You can get new servers for no money in seconds.
Its a wonderful world. Im so happy, there is LAMP. I never used Perl, Ruby, Lisp or Arc. So I cannot say anything about these. I can only say I dont miss a thing with LAMP. I have a LOT of complaints about HTML and Javascript. I hated using Microsoft stuff. LAMP was the breaktrhough.
Re: Why PHP won
#33This article is totally barking up the wrong tree. PHP's growth had little to do with its appeal to programmers, and lots to do with its appeal to shared hosting providers. Safe mode is what I'm talking about.
I have been a coder all my life and PHP very much appeals to me. I used Assembler, Basic, Pascal, C++ and a couple of other languages and now that I code in PHP, its the best part of my life. It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. I really love Linux, Apache and MySql. So doing things in LAMP is just great for…
Re: Why PHP won
#34Earlier quoted context omitted.
I have been a coder all my life and PHP very much appeals to me. I used Assembler, Basic, Pascal, C++ and a couple of other languages and now that I code in PHP, its the best part of my life. It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. I really love Linux, Apache and MySql. So doing things in LAMP is just great for…
Any tips or a blog where you share your ideas for the ones who want to follow your steps?
Re: Why PHP won
#35This article is totally barking up the wrong tree. PHP's growth had little to do with its appeal to programmers, and lots to do with its appeal to shared hosting providers. Safe mode is what I'm talking about.
I have been a coder all my life and PHP very much appeals to me. I used Assembler, Basic, Pascal, C++ and a couple of other languages and now that I code in PHP, its the best part of my life. It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. I really love Linux, Apache and MySql. So doing things in LAMP is just great for…
Very interesting. Please elaborate!
Re: Why PHP won
#36Good article. To add a few things: 1. PHP doesn't require routing. It's done for you by Apache to the PHP file at that location. Sure, you can go the way of nice frameworks like Cake and add routing for nicer URLs, but it's not required . PHP has some solution built in. 2. Deployment. The author touched on having to restart when using mod_perl, but it's more than that. In most cases, uploading files is enough. That's…
I'm a bit surprised that he didn't mention that PHP has very good documentation - virtually every function has a plain-english description (translated to multiple languages) followed by several usage examples and snippets that solve common real-world issues.
Re: Why PHP won
#37Earlier quoted context omitted.
I have been a coder all my life and PHP very much appeals to me. I used Assembler, Basic, Pascal, C++ and a couple of other languages and now that I code in PHP, its the best part of my life. It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. I really love Linux, Apache and MySql. So doing things in LAMP is just great for…
> It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. Very interesting. Please elaborate!
Re: Why PHP won
#38Earlier quoted context omitted.
> It enabled me to write multiple hugely successful websites that make me enough money for me, so I can do whatever I want. For the rest of my life. Very interesting. Please elaborate!
I prefer to stay anonymous. But its probably a very typical Nerd 2.0 story like the ones you hear at this website often. Only that I always stayed in my room and didnt connect to any other web2.0 people. No Blog, no press releases, no ycombinator, no investors. I just wrote some stuff that people want and got some good return from it.
Re: Why PHP won
#39Earlier quoted context omitted.
Any tips or a blog where you share your ideas for the ones who want to follow your steps?
Im not that good with words. That outburst of delight I wrote above is probably one of the better posts I wrote. Who knows, maybe Im getting better at this. Then I might start a blog one day.
Re: Why PHP won
#40Good article. To add a few things: 1. PHP doesn't require routing. It's done for you by Apache to the PHP file at that location. Sure, you can go the way of nice frameworks like Cake and add routing for nicer URLs, but it's not required . PHP has some solution built in. 2. Deployment. The author touched on having to restart when using mod_perl, but it's more than that. In most cases, uploading files is enough. That's…
I'm a bit surprised that he didn't mention that PHP has very good documentation - virtually every function has a plain-english description (translated to multiple languages) followed by several usage examples and snippets that solve common real-world issues.
Rdoc tries to be that for ruby projects, but it still feels like a step backwards. Google lessens the pain somewhat, but it's still nice to just hit php.net/manual/en or api.jquery.com and find everything I need.