International PHP Magazine: Poll Question: Why PHP Sucks
114906
The results of the latest International PHP Magazine are in and posted today on their site. The question this time was asking developers and visitors alike what they think sucks about PHP.   Choices included "No lexical scoping", "PEAR", and "Worst Configuration System" but one climbed to the top far above the others - "No namespacing". Trailing that at a distant second were two, getting the same number of votes - "No lexical scoping" and "Can't afford a vowel" (hmm, interesting).    Up for this week is a new poll that asks those out there that have used the Symfony framework to cast their votes about what they think is the best feature the project has included. Check it out and cast your vote today...
698334
Popular posts from PHPDeveloper.org for the past week:The Bakery: Six New Articles/Tutorials PostedEvert Pot's Blog: PHP: Arrays vs. ObjectsDevArticles: Learning AJAXInternet Super Hero: PHP: mysqli_fetch_all()David Coallier's Blog: PHP Namespaces (Part 1: Basic usage & gotchas)I/O Reader: 15 Cool Things & 12 Things to Dislike About PHPProPHP Podcast: Newscast - August 16, 2007PHPBuilder.com: Dynamic XML with PHPSite News: Popular Posts for the Week of 08.17.2007PRADO Watch Blog: PRADO Watch: Interview With Timani Tunduwani - Why I Moved From CakePHP to PRADO
437494
Popular posts from PHPDeveloper.org for the past week:PHPClasses.org: A PHP killer feature - Streams abstractionRob Thompson's Blog: Switch vs. IfPHPEverywhere: Octopussy numbers in PHPJob Posting: MODE Visual Seeks PHP Developer (Charlotte, NC)ProDevTips.com: Why PHP as a templating language sucksMatthew Turland's Blog: The Yin and Yang of TypingStubbles Blog: Stubbles 0.5.0 releasedChristopher Jones' Blog: Updated connection pooling in PHP's OCI8 extensionBen Ramsey's Blog: Congrats Costa Rica PHP!Carsten Lucke's Blog: Configuration issues with Xdebug on Debian Etch
741553
The latest issue of php|architect magaizne has been released today - September 2006.   Highlights in this issue include:  "Is PHP 5 really slower than PHP 4?" by Andi Gutmans and Dmitry Stogov "State of the PEAR" contributed by Aaron Wormus, a walkthrough of the history of PEAR "Know Your Stuff" from Philip Olson, looking at the PHP Manual "Desperately Seeking Susan" by Tom Gidden, a look at the basics of creating a search engine and, of course the Security Corner (Ilia Alshanetsky) is back with part two of the look at configuration in PHP   ...and much more.   You can either pick up this issue by itself (about $4.20 USD) or as a part of a shiny, new subscription (about $35.00 USD).
629310
You cannot help but like someone like Greg who is honest and humble:  "I am one of the core developers of the PEAR package who has joined the game relatively late... The base PEAR class is one monstrous mistake, and PEAR_Error is pretty close. Everyone knows this. I designed an error class that is much, much more flexible and it is part of PEAR 1.3.1 (PEAR_ErrorStack) - check it out. "  Sadly it's just not true that everyone knows that PEAR class is big mistake (Jeff Moore has more on why PEAR.php is awful).  Given that PEAR is both an important framework and a worthless class, the confusion in names will  definitely  cause the value of the PEAR class to be overestimated. Just read any article on PEAR and you can see what nice words they have to say about the base classes :-(     I once said once that too many PEAR developers were journeymen. This might have offended  some people, but I was trying hard to be diplomatic. I must say that today the PEAR group is definitely more mature, and they have learnt a lot about library design. What would really make my eyes light up  would be an PEAR2 initiative that kept the existing classes, but dropped the bad seeds such as PEAR.php (e.g. the PEAR and PEAR_Error classes).   And in case you were wondering, I do think there's great value in the PEAR DB API. API's are important for interoperatability. For example, ADOdb has a PEAR DB compatibility mode. I would certainly be flattered if PEAR DB had an ADOdb compat mode too :-)
431145
On the "start up web 2.0" blog today, there's a set of benchmarks comparing two popular PHP frameworks - CakePHP and CodeIgniter - and how the fare in the standard "Hello World" sort of test.   After reading How fast is your framework I was rather intrigued to compare CakePHP and CodeIgniter. [...] Each framework is required to have the output "HelloWorld!" produced from a view and a controllers will obviously have to be created.   He ran the tests with the Apache benchmark tool (ab) and the simple code he provides with the results leaning towards CodeIgniter (by a good bit). Overall, it had a faster response time than CakePHP by about half.   Check out his results and grab the code and run it for yourself - see what kind of results you get and how they compare.
722744
On his blog, Ian Bicking has posted some of his thoughts on a positive look at PHP - what he thinks PHP has done right.   With the recent talk on the blogosphere about deployment (and for Django, and lots of other posts too), people are thinking about PHP a bit more analytically. I think people mostly get it wrong.   He points out that PHP, in essence, is a CGI-style execution and, in being so, makes it more flexible. Both sides, web and command line, can work with the language equally well. He also mentions the developer/administrator split he sees in PHP's structure and how the language facilitates it.
451170
The International PHP Magazine has posted the results for this week's poll that asked which, of the options given, was what made the CodeIgniter framework the best.   There were only four options this time:   Saves Time and Code for Simple things Based on MVC pattern Easy to Extend Flexibility to create own libraries and helpers   Coming in in a close race for second and first were the "flexibility" and "saves time" options (with the first beating the other by less than 2 percent).   Be sure to check out and cast your vote in their latest poll posted this week that asks "What's the best way to do QA in PHP?"
385236
Scott Mattocks is back with the latest installment of the PHP-GTK news, issue number 22.   It's been a while, but I finally have some time to get back to summing up the world of PHP-GTK. Things have slowed down a little in the past few months on the development side but that doesn't mean that the world of PHP-GTK 2 has stood still.   In this edition, there's a call for help for anyone that would want to join the other (4!) developers in working on the PHP-GTK 2 project as well as some general information about the project and its involvement in the community - from talks at php/db|works, International PHP Conference, and the Zend/PHP Conference to the many PHP-GTK-related articles being printed to a new online resource for PHP-GTK tutorials.
636915
Popular posts from PHPDeveloper.org for the past week:RefreshinglyBlue Blog: PHP vs Ruby - Practical Language DifferencesAndreas Gohr's Blog: Determine StumbleUpon RankingsPHP.net: PHP 5.2.4 ReleasedThe Bakery: Five New Posts - Custom Views, CSS, ViewInFile, ActsAs and Email ValidationPHPBuilder.com: File uploads made easyStefan Mischook's Blog: Turning on display_errors in WAMP - Video Tutorialphp|architect: Pro::PHP Podcast - Newscast for August 2007MT-Soft Blog: Creating a secure PHP production environment from Source CodeCommunity News: Andi Gutmans to Present at AjaxWorld 2007HowTo Forge: How To Set Up A Facebook RSS Feed Reader
195318
For your consideration today, Philip Olson has worked up a listing of twenty (humorous) possible reasons that the names of the PHP functions are weird.   Here are 20 possible reasons why PHP functions lack consistent names and parameters. Learning the definition for every PHP function is truly an amazing feat and I doubt this has been attempted or accomplished by anyone. At least, by any sane human. And references are named references because they are designed to be referenced, right?   Items on the list include:  PHP likes BC PHP says all your namespace are belong to us PHP function naming algorithm still remains a secret and cannot be cracked PHP isn't designed to win a beauty contest
273337
Here's what was popular in the PHP community one year ago today:Job Posting: National Auto Warranty Seeks MySQL DBAJob Posting: National Auto Warranty Seeks PHP Web App Developer (Wentzville, MO)DevShed: Creating a Login Script for a PHP Invoicing SystemZak Greant's Blog: The eZ partner program (response to Seth Gottlieb's Commercial O/S business post)php|architect: Application-level Logging with the Zend FrameworkPaul Reinheimer's Blog: Object-Oriented PHP, Concepts, Techniques, and CodeRyan Malesevich's Blog: Fight Spam Comments with Bad Behavior and AkismetZend Developer Zone: SQLite: Lean, Mean DB MachineBuilderau.com.au: Cache PHP scripts with APC modulePro-PHP Podcast: Interview With Cal EvansSitePoint PHP Blog: PHP extension for Cairo graphics libraryTechnobabbler.com: making a radar loop with PHPDevShed: Working with MySQL Result Sets and the Decorator Pattern in PHPJob Posting: exhibit-E Seeks Interactive Developer (New York, NY)Jacob Santos' Blog: Patterns for PHP: Page Controller Draft
762479
Here's what was popular in the PHP community one year ago today:PHP-GTK Community Site: Add icons to GtkMenuphp|architect: php|tek 2007 schedule now onlineRyan Malesevich's Blog: Comments Closed After 21 DaysCodeSnipers.com: Book review: Beginning Ajax with PHP by Lee BabinCommunity News: TorrentVolve (PHP-driven Web-based BitTorrent)Stefan Mischook's Blog: Book Review: PHP 5 in PracticeJSLabs Blog:  How to create a php upload progress meterAlexander Netkachev's Blog: PHP IDE with debugger 0.1.6 is outDeveloper.com: Forms Validation with Symfony and PrototypeMarco Tabini's Blog: 5 PHP Performance Tips You Probably Don't Want To HearThe Codist Blog: I Will Never Understand the Appeal Of PHPArnold's Blog: Without a framework: (M)VCPHPBuilder.com: Reading RSS feeds in PHP: Part 1Mike Potter's Blog: AMFPHP 1.9 Examples from Renaun EricksonPHP 10.0 Blog: php -T (variable tainting)
155453
Popular posts from PHPDeveloper.org for the past week:PHPBuilder.com: AJAX and PHP Part 1Developer.com: Threads Versus The Singleton PatternNick Halstead's Blog: Google Gears Caching of WordPress in PHPDevShed: PHP, MySQL and the PEAR DatabaseDave Dash's Blog: Installing a PHP that can do symfony+doctrine on DreamhostChristopher Jones' Blog: Upgrade PHP with Oracle Application Server on LinuxPHP.net: PHP 5.2.3 ReleasedPro::PHP Podcast: Newscast for May 31st, 2007Secunia.com: PHP Integer Overflow Vulnerability and Security BypassPHPBuilder.com: PHP and Regular Expressions 101
82173
In this new post to the PHP Everywhere blog, John Lim asks an interesting question - why should PHP ever be taught in schools? (in response to this post)   If something is popular but hard to understand then we need an education process. To just shake our heads and give up is simply immature (or trolling). Otherwise we might as well say that English (or any other spoken language for that matter) should not be taught, because spoken languages are illogical, imprecise and therefore ... useless.   John also clears up some of the misconceptions from the other post with equality and type comparison in PHP.
220615
The International PHP Magazine has published the results of this past week's poll that asked "Which is truest?" (or "which of the options given about PHP is the most correct).   The International PHP Magazine conducted a poll over the week, asking for your opinion regarding the truest statement. The poll results with the respective percentages are as shown in the screen cast.   Of the options given, only one stood out above the rest - "PHP is Easy to Learn" - definitely a true statement. As far as the rest, they were close, but "PHP code gets embedded in HTML pages" came in second.   Be sure to check out the new poll question for the week - "You Did Not Know That..." (selecting which of the little known facts about PHP you didn't know).
259126
In an "interesting" post to The Codist blog, there's one developer's look at PHP and his confession that he'll never quite understand the appeal of the language.   How PHP can be so popular is beyond me; the whole sense of encouraging all of your html, code, bindings, javascript, even sql (as in the below example) into a single file is a nightmare.   He Goes on to talk about his experience with JSP versus PHP and some perspectives on how PHP lacks features he's used to or how other developers he's talked to had similar issues.   One thing that concerns me (and apparently several others in the PHP community) is that he keeps talking about procedural PHP code that's an "all in one page" kind of setup. Well, of course this can get messy quickly - that's no way to code anything, much less PHP. Organization means more than just breaking code up into chunks on your page (though it's a very low-level start). Plus, the sample code he provides is a joke - a PHP developer with a few weeks of experience could push out something 10x better.