PHP: the quiet powerhouse
blog.appfog.com
PHP: the quiet powerhouse
1–10 of 140 posts
Re: PHP: the quiet powerhouse
#2Which... is even odder because some evangelists like to point out that python and ruby are older than PHP, as if that means much.
While I generally agree with the points, many PHP strengths are also weaknesses. For example - "Direct HTML embedding." It's nice and easy, but because it's so easy, it leads to unescaped output, and xss exploits and such.
PHP does let you as productive as you want to be on the web, either with raw PHP or with one of the myriad frameworks. The author's point that no other language gives you that is, I think, another one of PHP's strengths (but yes, is essentially a weakness in the wrong hands as well).
EDIT - have been using PHP since early 1996 - almost since its inception, and have watched the criticism (and occasional hate) ebb and flow over the years. That seems to be the only constant to PHP. :)
Re: PHP: the quiet powerhouse
#3Re: PHP: the quiet powerhouse
#4I have a few nits with this post, but am mostly irked by the comparisons between PHP (a language) and Rails (a framework)
So you're quite right, but I hope you would agree that the Rails/PHP comparison, in spite of its imperfections, is compatible with the point I was trying to make.
Re: PHP: the quiet powerhouse
#5It's why PHP would be the best tool for the job once you have a specific objective in mind.
When you have a specific problem to solve other than 'supported by millions of cheap webhosts' PHP is rarely the best choice.
It's like a swiss army knife, it's highly useful in many situations and a good tool to have in your pocket, but if you know you're going to need to unscrew something you should probably bring a screw driver.
Re: PHP: the quiet powerhouse
#6There are something PHP does nicely than Ruby does. Visa versa. However in all the PHP apps I have made / used, their structures started out with good intentions and then descended into pure chaos. There isn't a unified package manager for Python and PHP that is widely accepted. Ruby has rubygems and bundler.
Maybe next time when I start building another PHP app with namespacing, I'll behave better and make my designs more decoupled so that components can be removed and added, provided their interfaces match.
Re: PHP: the quiet powerhouse
#7The issue with PHP isn't that you can't make it do a whole bunch of things that are wonderful... It's why PHP would be the best tool for the job once you have a specific objective in mind. When you have a specific problem to solve other than 'supported by millions of cheap webhosts' PHP is rarely the best choice. It's like a swiss army knife, it's highly useful in many situations and a good tool to have in your pocke…
Re: PHP: the quiet powerhouse
#8I enjoyed PHP. I enjoyed Ruby. If I was to do a complex project that would require a lot of integration with external services, I would want a good OOP language like python or ruby. There are something PHP does nicely than Ruby does. Visa versa. However in all the PHP apps I have made / used, their structures started out with good intentions and then descended into pure chaos. There isn't a unified package manager fo…
Re: PHP: the quiet powerhouse
#9"Dozens of new language-specific communities have now entered the fray and brought along their legions of devotees with them, and many of those devotees see PHP as being passé. I even had the following happen to me, and this is absolutely a true story and can be verified by our VP of Operations, Richard Kotulski: I was in an elevator with O’Reilly’s very good “PHP Cookbook” in hand and an older gentleman scoffed at m…
PHP is a Web scripting language (which I consider to be very different from a general-purpose programming language or even a scripting language), designed and developed to generate markup.
I have seen a lot of "templating" libraries (Smarty among them) and all they do is mimic the basic syntax of PHP using something else that is not PHP.
I know the theory ("designers don't know how or want to program"), but learning PHP conditional statements or loops is as difficult or simple as any "templating" library that asks you to learn its exotic syntax.
Now, MVC is good and one should avoid blending presentation code with models and controllers, but most MVC frameworks fail when they require you to instantiate a gazillion extra objects, just to render a Web page.
Re: PHP: the quiet powerhouse
#10I have a few nits with this post, but am mostly irked by the comparisons between PHP (a language) and Rails (a framework)