Yet Another Web Development Blog: Dear PHP, I think itâs time we broke up.
448854
As anyone that's worked with a programming language for a long time knows, you get to know the ins and outs of it pretty well. You get a good feel for how it all works and how feel confident in your skills with it. But what happens if you decide to move on and leave the relationship? Check out this take on just such a situation from the Yet Another Web Development Blog.   We've been together for about five years now. I've had a lot of good times and I've really enjoyed being with you. However, the more we work together, the more concerned I get about our future. I'm sorry, but you don't have the elegance that inspires me to want marry you. I think it's time we broke up.   Some of the reasons given for moving on is PHP's seeming identity crisis, consistency in function names/functionality, and performance issues that were just too much.    Despite being a bit anti-PHP, it's still a well-written piece. Check it out...
188665
The PHP Community is buzzing about a new article, posted on the O'Reilly Ruby blog, about how the author (Derek Silvers of cdbaby.com) made the decision that Ruby on Rails just wasn't right for the project he was working on.    Back in January 2005, I announced on the O'Reilly blog that I was going to completely scrap over 100,000 lines of messy PHP code in my existing CD Baby  website, and rewrite the entire thing in Rails, from scratch. [...] The first few months showed good progress, and Jeremy could not have been more amazing, twisting the deep inner guts of Rails to make it do things it was never intended to do.   But at every step, it seemed our needs clashed with Rails' preferences. (Like trying to turn a train into a boat. It's do-able with a lot of glue. But it's damn hard. And certainly makes you ask why you're really doing this.)    Recounting the rest of the story, Derek mentions the turning point ("Is there anything Rails can do that PHP CAN'T do?") and the speed at which they were able to make up for the two years of lost development time. To helps others make a decision for their project, he also includes seven reasons why he made the decision to switch back, including:   Our entire company's stuff was in php: don't underestimate integration Don't want what i donÃ¢ÂÂt need I love SQL Programming languages are like girlfriends: the new one is better because *you* are better   There's also been several bloggers in the PHP community that have responded to the article:   Elizabeth Naramore - "Derek Sivers' Article on RoR vs PHP" Paul Jones - "Is there anything Rails can do that PHP cannot do? *No.*" Terry Chay - "Why PHP triumphs over Ruby" Jeff Moore - "Ruby versus PHP or There and Back Again"
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.
437635
Hasin Hayder asks a question in his latest blog post that some in the PHP community have been wondering for a while now - is the International PHP Magazine dead?   I am a subscriber of International PHP Magazine for years. I bought the subscription looking at the back issues. They were sexy, resourceful and yup, very good. But I think these guys don't care about the magazine anymore. It became just a funny stuff for them. All the readers/subscribers and viewers doesnÃ¢ÂÂt bring any value to them. Look what they are doing actually...   He points out six things that the magazine and its staff are doing including RoR articles in an issue, content on the site that's way out of date and the smaller size of recent issues. Comments to the post point out that there has been issues released but that the magazine is published by a non-technical company that just might be pushing this particular publication aside.
616513
Popular posts from PHPDeveloper.org for the past week:Community News: Namespaces in PHP6Mike Potter's Blog: Sample Code From PHP / Flex e-SeminarThe Bakery: PremierMarinas.com, ScienceHack.com and an iPhone AppPHP F1: PHP Session TutorialCommunity News: GoPHP5 Official SiteCommunity News: jPOP Framework - Javascript & PHPTim Koschuetzki's Blog: Composing Methods: Remove Assignments to ParametersAlexey Zakhlestin's Blog: YAML: Syck for PHP is not read-only anymoreMatthew O'Phinney's Blog: File_Fortune refactoredSite News: Popular Posts for the Week of 07.06.2007
466256
Ligaya Turmelle has relayed some great news in her latest blog entry, something that the web's been needing for a long time - a new group from the W3C created specifically for enhancing the HTML standard.   Now I have to admit to being curious about what is going on - after all anything new dealing with the web affects me as PHP coder. Since the W3C is supposedly interested in input from the Web community and content developers, I decided to see who from PHP would be there. Granted it is very early for the formation of the group so it didn't really surprise me to see no one from PHP that I know or heard about in there, but I wonder if anyone from the PHP Group will become a "invited expert" somewhere down the road.   The group is looking for members to help define this next generation of markup on the web. Check out their page for some of the qualifications needed to participate and for some of the upcoming events.W3C Launches New HTML Working Group
661935
In this new post to his blog, Richard Heyes talks about an example he's come across of PHP being used as backend behind a large marketing project:    I recently read an interesting example at Neil Shearing's internet marketing strategies blog of combining .NET desktop software with a PHP backend.   We all know PHP is often slated by "real programmers" as a scripting language only useful for kiddie's home pages, and its nice to see a serious marketer choosing PHP to power the backend to a serious piece of viral software with the potential to go load-mad.    Richard also points out some of his experience trying to market his software and which of his customers are the ones that would provide the most return (the ones looking for updates) and how he can gather their information more productively to further his project's goals.
242658
Popular posts from PHPDeveloper.org for the past week:Sebastian Bergmann's Blog: Support for the Cancel Case Workflow PatternCommunity News: The PDO v2 ProposalSite News: Popular Posts for the Week of 01.25.2008ProPHP Podcast: PHP Newscast for 2008/01/24Developer Tutorials Blog: Why you should be using YAML for configJob Posting: InvestorGuide.com Seeks Web Developer (Fairfax, VA)Pierre-Alain Joye's Blog: Debugging symfony (or any php script) with vim and XdebugCIO.com: You Used PHP to Write WHAT?!Demian Turner's Blog: Seagull 0.6.4 Release (fixes Security Isse from 0.6.3)Developer Tutorials Blog: PHP Qualifications: The Good, The Bad and The Ugly
533264
Sean Coates has a reminder posted to his blog for all of the aspiring PHP speakers out there to get their proposals in for this year's (well, next year's) php|tek 2008.   I just want to drop a quick reminder that the php|tek 2008 Call for Papers is about to close (on Oct. 31), so if you've been dragging your feet, now would be a good time to stop doing that and send in your proposals.   Some of the topics they're interested in this year are rich application development, PHP4->PHP5 migration and looks head at PHP6. Check out the Call for Papers page on the php|tek site for the full list of information you'll need to include along with the summary for your proposal.
218405
About two years ago you may remember we were in the throes of the SOAP revolution. "Web services everywhere!" was the cry and have to confess I'm one of those guilty of having gone for it, for a while. There were going to be these giant UDDI servers that would aggregate everyone's web services and the Internet would never look the same again...
654370
Pierre-Alain Joye has a little reminder posted to his blog today about two posts from planet-debian and Apache that refer to clones/references in PHP4 and PHP5 and some of the misconceptions presented there.   Reading planet-debian and Apache (from Sven and David), I catched two posts about clones and references in php4 and php5. I do not think it is worth to explain again everything here as Sara wrote a very good post already, check it out here.   He mentions his annoyance with articles/posts like these and the impact that it has on PHP as well as the person posting.   I wonder when the OS community in general will be mature enough to stop bitching at each other. And that's valid for PHP developers, gnome-kde and other well established wars.
722556
John Mertic has a quick note on his blog about the latest release candidate for the Windows PHP installer (PHP5.2.0RC3) and some issues they've been having.    Rebuilt the installer for 5.2.0RC3. Edin was having problems building it so I'm going to do it and upload it; hopefully we can resolve the issue.   It's also noted that if you see issues with using the installer, try removing the previous PHP installation before running it again.
249394
Jacob Santos makes some of his own comments about the recent PHP5 adoption talk that's been going around in the PHP community (spurred on by comments made by Matt of the Wordpress project).   Matt brings up some good points. What might be limiting PHP 5 adoption, could just be the lack of interest in developers. [...] Up until reading his rant, I've lived in a box where everyone I've talked to, used and enjoyed PHP 5 and its vast extensions. Developing in PHP 5.0 was uneventfully, but you learn to appreciate PHP 5 with the core inclusion of PDO with PHP 5.1. PHP 5 is not without annoyances. In the core developers attempts to "better" the language, they made changes that broke code that previously worked.   He looks at a few of the items for debate surrounding the move from PHP4 to PHP5 including the extensions that come bundled with PHP5, solving the register_globals issue, and a brief mention of the Standard PHP Library.
498714
Tony Bibbs, in the wake of last week's surprise from Microsoft to Yahoo, has posted a few of his thoughts on the matter.   I woke up this morning to the news of a $44 billion buy-out offer from Microsoft for Yahoo!. This is being covered from all angles in various tech sites like Slashdot but I think the one angle I haven't seen yet is what does this mean for PHP?   He mentions the work that Microsoft and Zend have done to push PHP support on the OS (check out this email too) and he wonders what the final impact of it all could mean for the language - will things change drastically if Microsoft becomes a major player in the PHP world or would they stay behind the scenes and give the community the support it might need.
636649
Following up on this article from Akash Mehta, Bryan has posted five more suggestions he has to help make you a better PHP developer.   I thought all of Akash's suggestions were good but a little broad and seemed to involve a lot of reading. And while any budding developer will jump at the chance to expand their burgeoning technical library, I thought there were a couple of items we could add to his list.  The recommendations that made his list are  Start a project that other people (developers and end users) will use. Learn another language. Teach someone PHP. Ask for suggestions not solutions. Use what you read.   I'm particularly a fan of the third one (teaching) - not only does it spread PHP out even more through the masses, but it can really test you on your knowledge (some of those "how do I.." questions can get a bit complex, even from beginners).
295108
As of today (mentioned in this post on PHP.net) the PHP4 life cycle is finally coming to a close:    Today it is exactly three years ago since PHP 5 has been released. In those three years it has seen many improvements over PHP 4. PHP 5 is fast, stable & production-ready and as PHP 6 is on the way, PHP 4 will be discontinued.   The PHP development team hereby announces that support for PHP 4 will continue until the end of this year only. After 2007-12-31 there will be no more releases of PHP 4.4. We will continue to make critical security fixes available on a case-by-case basis until 2008-08-08. Please use the rest of this year to make your application suitable to run on PHP 5.     They link to a migration guide for users moving up from PHP4 to PHP5 including guides for the PHP 5.0 to 5.1 switch and the PHP 5.1 to 5.2 switch.
596569
With a bit of a rebuttal for Harry Fuecks' statement that PHP has a great lack of international support comes this new posting from John Lim at PHPEverywhere.