Jaybill McCarthy's Blog: 10 PHP Myths Dispelled
20940
As mentioned on the Zend Developer Zone, Jaybill McCarthy has written up a Blog post about ten of the PHP myths that are common on the web and the facts that dismiss them.   I am a PHP developer. Maybe even a halfway decent one. As such, I often find myself engaged in conversations on the subject of web application development in general and PHP in particular. I am continually flustered by the myths, half-truths and outright falsehoods that technical and non-technical people alike hold about this humble programming language.   Some of the points included in his "top ten" list are things like "PHP Encourages Sloppy Code", "PHP is slow because itÃ¢ÂÂs interpreted" and "PHP apps all look the same".
230013
In this new article from DevShed.com, they provide a high-level introduction to PHP - what it is, where it came from, some of the sample features (of both PHP 4 and PHP 5), as well as some of the drawbacks for the language.
179571
Here's what was popular in the PHP community one year ago today:Splitbrain.org: Add comments to any PHP scriptRyan Malesevich's Blog: Separate Trackbacks from Comments RevisitedDeveloperTutorials.com: Inserting An Array Into A DatabaseSymfony Blog: The Definitive Guide to Symfony and symfony 1.0 RC1 releasedSoledad Pendaes' Blog: PHP will never have a (real) Rails-like frameworkJSLabs Blog:  A web server in PHPRobert Swarthout's Blog: PHP frontend to Subversion (SVN)Christopher Jones' Blog: OCI8 1.2.3 Patch is Available on PECLDotVoid.com: Parsing the user agent string using PHPPaul Jones' Blog: Solar 0.26.0 Released, and New WebsitePierre-Alain Joye's Blog: Zip 1.8.5, small bug fixes releaseZend Developer Zone: Zend Monthly Newsletter - JanuaryMike Potter's Blog: Flash, Flex and PHP Just Got A Huge BoostJonathan Snook's Blog: Review: PHP SolutionsOracle Technology Network: Creating an Ajax Process Using PHP and Oracle
719619
Krystian Hoffman has posted to his blog today a few reasons (10 to be exact) that he likes and uses PHP. Fortunately, most of them are some of the best reasons for anyone to use the language.   ended up with ten points on why I use PHP and I guess this would be a good post here on my blog, as it seems people like lists in general and maybe I could get some people out there that aren't really sure about whether PHP is good or bad, to get some insight at least.  Here's some of his list:   The PHP Community The (language's) Performance Its Portability It has strong Object-oriented support   Other things got a mention as well - the low learning curve, low cost, included libraries - but the above few seemed the strongest.
415712
To set things right about a misquote on Slashdot, Zeev Suraksi has posted this long statement mentioning what he really said and a few more personal opinions.   I've just been misquoted on Slashdot, as if I said there are no security problems in PHP itself, and that I instead point my finger only at inexperienced developers. If you read the original article on Heise Security, you'll see that I have not said anything of the sort. [...] I believe this is the belief of most others on the security team, but I'm only speaking on behalf of myself and do not represent them.   He also covers five more points pertaining to the article and the situation:  Where the bugs/problems lie with problems in PHP Why there are security problems in web PHP applications Why the current security level can be partially blamed on the language itself An admission that yes, there are security problems in PHP And the track record the PHP developers have had in fixing these issues  There's much more than just these brief highlights here, so I encourage you to head on over and check out the full post for yourself.   There are some other opinions on the matter from a few others out there too:  cyberlot's blog Zend Developer Zone's post Tony Bibbs' blog
514699
Cal Evans of the Zend Developer Zone has posted a new book review for one of Sams Publishing's latest PHP-related offerings, "PHP 5 In Practice" by Elliott "Eli" White III (Senior Programmer over at digg.com.   First let me say, if you are new to PHP or programming in general, skip this book. This is not a how to or even a cookbook for simple concepts. To get the most from this book you need to have a firm grounding in programming.   He sets the tone for the rest of the interview right there, noting that most of the book is made up of little examples, helpful bits to fill a need rather than teaching you the basics (or more advanced features) of PHP as a language. Cal spotlights this kind of content by talking about the "binary tree implementation" section. Check out the rest of the review for the full story.
611923
This week, Cal Evans is reporting live from this year's php/db|works conference in Toronto. Since today is "Tutorial Day", the schedule is a little lighter, and he makes to time to catch Rob Richards' talk on PHP and Advanced XML and Web Services.    Rob Richards is the author of Pro PHP XML and Web Services. He literally wrote the book on using PHP and XML together. At php|works, he is leading a tutorial on using XML in web services using the DOM extension.    If you ever get a chance to hear Rob do a presentation, let me warn you, it is not for the faint of heart. As I learned last night when I sat down with Rob to record an interview, Rob likes to speak on leading edge and advanced topics. This tutorial is an excellent example of that philosophy.    Cal talks more about the content of the talk - its simplicity despite the complex topic, how much info is jammed in, and the fact that it's not just one giant pitch for Rob's book.
389521
Time for a little nostalgia today in this new post from Philip Olson looking back at a brief history of the PHP acronym - where it came from and how it evolved to mean "PHP: Hypertext Preprocessor".   While reminiscing what PHP was like back in the early early years, I stumbled upon a little historical nugget from the old website. Do you know what the acronym PHP stands for? Many of us do, or think we do. [...] But how was the definition chosen? For fun, here's a look back at the official vote that determined this new meaning way back in 1998. It might be worth mentioning that Rasmus, the father of PHP, did not vote for the eventual winner.   He also includes a few "notable quotes that could be taken out of context" from Rasmus Lerdorf concerning his opinions on the matter of the acronym's meaning as well as some other brief notes on the history of PHP and its name change.
343971
With the recent acquisition Sun has made (you heard about that, right?), there's tons of resources in the open source community that are talking about it, lots of them are more PHP-specific. Cal Evans has put together a list of some of the PHP bloggers/community memembers that have posted some of their thoughts on the purchase.   With all of the buzz floating around yesterday on this topic, I decided to let some of the dust settle before posting. From everything I've seen, the PHP community is largely positive about the news. [...] As I said, the community at large seems to be pleased with this news. Here are the links I've collected so far.   Names in the list include Andi Gutmans, Lukas Smith and Jaremy Zawodny. There's also a list of some comments from the "pundits" as to what this purchase could mean for the web as a whole.
741179
Christian Wenz has pointed out an older post from Larry Wall talking about the line between scripting and programming languages (mentioning specifically PHP).  From the article "":  I think, to most people, scripting is a lot like obscenity. I can't define it, but I'll know it when I see it. [...] If I had to pick one metaphor, it'd be easy onramps. And a slow lane. Maybe even with some optional fast lanes.   Larry goes through tons of different older languages commenting on their viability in the online community including: Javascript, LISP, Pascal, Python, Ruby and PHP. He then looks at the present and what sorts of things are happening in languages these days. This list includes things like early binding/late binding, eager typology/lazy typology, limited structures/rich structures, class-based/prototype-based and transaction/reaction/dynamic scope.
464596
PHP isn't exclusively for Web pages. You can use it like Perl for cron jobs and other tasks.
392669
Open source is wonderful. Everything is so open, warts and all. Roshan Naik complains about the state of PHP:
732440
The International PHP Magazine has posted results from their latest PHP community poll as voted on by visitors to their site. The question for this poll asked developers what they thought, of the choices on the list, was the most common mistake that PHP developers make.   Coming in at number one by an overwhelming lead was "Not escaping entities and SQL input" (a definite problem indeed) with the next highest option, "Not using a Framework" a full twenty percent lower. The next two options were closer (descending) - "Using old PHP versions" and "No or little use of Object Orientation".   There's a new poll this week for your consideration - this time asking which stage, of the five options, should come first in the development cycle of a typical content management system. Head on over and cast your vote today!
727709
No Starch Press has officially released their PHP title "Wicked Cool PHP" (Real-World Scripts That Solve Difficult Problems).  Here's a bit from the press release:  Wicked Cool PHP [...] is a different breed of PHP book. It's made specifically for the developer who wants to know how to get things done without mucking around and wasting a lot of time. This is not a weighty PHP complete reference or bible that threatens to take down your bookshelf and the rest of the bookcase. This is a book for coders to pick up and use, not wade through.   It provides the reader with "76 immediately useful PHP scripts" that do a variety of things like send/receive email notifications, do some web scraping, track users with cookies and sessions and use web services like SOAP.    You can find out more about the book on this page on the O'Reilly website. The book will officially hit the stands February 15th.
41064
Gerd Schauffelberger writes on the PHP-Tools Blog today about the contents of the latest issue from the German PHP Magazine, specifically an article covering the PEAR package HTML_AJAX.   This article's target is (1st) to give a brief introduction to AJAX and how things work from Javascript an PHP side in contrary. Also (2nd) I wanted to show that you actually don't have to muck around with a mess of Javascript (browser compatibility issues and such) because it's it is all done by the Joshua Eichorn's HTML_AJAX framework.    The article doesn't build up an entire application (as Gerd mentions) but it does provide you a good base to work from and gives you a good direction to head from to learn more about this powerful package.
678730
The International PHP Magazine is back once again with the results from this week's poll that asked "Do you believe the following about PHP?" Options included:  PHP administrators like to compile PHP in Summer Register global is not dead memory_limit is not used PHP applications handle 100 Mb files  And coming out on top with 17.7% of the votes was the "Register globals" option, and coming in right behind was "handle 100Mb files" with 12.7% of the votes.   They've also posted a new poll for this week that asks "Why should a developer use CakePHP?" Check it out and vote for your choice of the six options.
90155
Based off of a previous article from Mike Willbanks, Stuart Herbert has posted some of his own thoughts on tuning and tweaking your applications for the best performance you can get out of them.   There's some good advice in there, and I thought it'd be a good idea to quickly add a bit more detail about the separate approaches that Mike raises.   He goes over the APC caching, memcache, the "gzip trick", the "Not Modified" header and optimized SQL statements.   He also mentions one thing that Mike didn't mention - a split between static files (no PHP needed) and their dynamic cousins. Having a more pure Apache (no PHP installed) can help give a minute jump in speed that, depending on the size of the site, could really add up from a user's perspective.