Community News: Responses to Namespaces
81366
There's been a few posts about the upcoming namespace support in PHP from different bloggers in the community including:   A post on the Stubbes blog by Frank Kleine and his discoveries of how the "use" keyword needs to be used in your applications A follow-up post from Frank as well correcting some of the problems in his first examples Some opinions from Richard Heyes on how useful they seem to him Brian Moon's comments on the level of traffic that the namespace discussion has been getting on the php.internals mailing list.   Right now there's so many ideas flying around about what namespaces should be and how they should be implemented that it'll be interesting to see which ideas finally come out on top.
388816
Popular posts from PHPDeveloper.org for the past week:Dave Dash's Blog: nginx and symfonyZend Developer Zone: The ZendCon Sessions Episode 6: Project Management Methods to Maintain IT StandSitePoint PHP Blog: Tokenization using regular expression sub patternsIT Jobs Watch: Results for PHP Developers in LondonJob Posting: Digital River Seeks PHP Developer (Eden Prairie, MN)Dan Scott's Blog: Oooh...looks like I've got (even more) work cut out for meLeon Chevalier's Blog: Improve website load time by 500% with 3 lines of codePHPWomen.org: elePHPantsPhil Thompson's Blog: 7 PHP functions that saved my lifeStuart Herbert's Blog: Using suphp To Secure A Shared Server
197002
On the SitePoint PHP blog today, Troels Knak-Nielsen has written up an article that talks about dependencies in your applications - those little interconnections your code relies on to do more with less.   In lack of better words, I'll call this compositional programming style. It's a style which is usually more prevalent with experienced programmers. [...] There is, however, a dark side to composition - dependencies.   He starts with a definition to bring everyone up to a level field then moves on to how their used (through a "global symbol" or directly passed in) and how they can "leak" if you're not careful.    To help protect you and your code from any kind of damage down the line, Troels suggests making a container to keep objects where they need to be. He even includes an example with namespace support to make things even easier down the road.
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
275233
In my last blog post, I mentioned the work on rubinius (then at a 0.7 release and now at 0.8) and JRuby.  I also promised I&#8217;d follow up on them.  Here&#8217;s what&#8217;s been going on so far.
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.
763474
In his latest post, Padraic Brady takes a look at PEAR in a verb form - both in how you can use it and what sorts of things it has in store.   over the last few months after finally getting over my ignorance of PEAR beyond it being a hodge podge of packages of dubious quality I've been questioning whether pearifying my future and past code is worthwhile. The answer is a resounding YES.   Unfortunately, there are some barriers for most people to get into the PEAR world (including the lack of the "coolest packages") with some of the perceived barriers including:   PEAR will require large scale changes to my shiny new cool code PEAR only allows proposals for complete functional code PEAR is elitist PEAR is fossilised   He also talks about PEAR packages and dispels one of the most popular myths about the package repository - "you can't use PEAR on a shared host".
516456
In response to his introduction of the non-well-formed XML patch the other day, Christian Stocker has a new posting with a bit of a rebuttal on the subject.
584229
Popular posts from PHPDeveloper.org for the past week:Reinhold Weber's Blog: 40 signs you really are a lousy PHP programmerScott Klarr's Blog: PHP Cheat SheetsDeveloperTutorials.com: Building Desktop Applications in PHPPadraic Brady's Blog: The Zend Framework and Microformats: Zend_Microformat ProposedCommunity News: GoPHP5 Project Wraps UpJob Posting: Technology Resources, Inc Seeks Senior PHP Developer (New York, NY)Job Posting: Red Ventures Seeks Sr. Systems Analyst/Web Developer (Charlotte, NC)Community News: Forage - A Search Abstraction LayerCommunity News: php|architect Launches C7Y Site (News/Podcast/Forums)Richard Heyes' Blog: SMTP for PHP 5
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
588152
Russ asks: Where's the OpenSocial container API? I love Russ because he cuts through all the BS and gets right to the core, most basic question, and he doesn't care who he pisses off. That's my kind of developer. You can't lie to the compiler, when the bits hit the road, you gotta know what garbage goes in and what garbage comes out.  (Ahh programmer's humor!) In other words, suppose I wanted to compete with Google, MySpace, Plaxo and LinkedIn, well, where's the spec that shows me how to do that? Well, of course I don't know, they aren't communicating with riffraff like me, but I have some experience with this kind of stuff, so I can hazard a guess. If they publish a spec,all kinds of projects will likely get started to enable the API in (just for the sake of argument): Drupal, WordPress, Twitter, Pownce, Jaiku, Scripting News (why not add widgets to a random blog), CNN, The New York Times, well you get the idea. There might be lots of implementations very quickly. And that would be it for changes. It would be frozen de facto, they'd have to live with what they have, which given how quickly it was thrown together, probably isn't very good. Not the kind of stuff you'd like to support for the next decade or two. Or maybe they would break everyone, something guaranteed to make them a lot of enemies, much the way Microsoft did, and they were good at migration of APIs.  Google is good at doing AJAXy web UIs, they make users happy, but they're not very good at APIs. This one is a loser, for sure. That's the answer to Russ's question. It's probably not malice that keeps them from releasing details to everyone outside their club, it's pragmatism. They have to try to hold on to it to keep it from becoming even more of a mess than it already is. Just my opinion, for what it's worth. I've been wrong many times before.
121972
David Sklar points out some of the new base sites that are being offered on the PHP-based mashup site, Ning.    It's been a lot of hard work, so I'm quite excited that we've just released three great new Ning sites: Ning Videos, Ning Photos, and Ning Group.   Plus, all three sites have the juicy bits that every site on the Ning platform gets -- things such as cloneability, complete customization, and built-in REST APIs. I've been watching the feeds for clones of photos and videos -- I suppose seeing who's cloned sites you care about is the Web 2.0 version of ego surfing.    He also talks about some of the features of the Ning Photo cloneable site like the slideshow and, in Ning Video, the embeddable player. The Ning Group application also has parsing abilities to help with sharing documents/music/photos/etc with anyone.
202255
OK, we had an extended breather from our last look at BIND's zone file pri.example.org. It's time to finish up and get a sense of what these records mean. To go off-topic a little, recently, I had the task of setting up two OpenLDAP servers and putting together a test environment for a project with several developers and several applications including some LAMP applications. Without a working knowledge of DNS, the project would have gone amuck.
621839
"Rubinius is a project to watch", so says Charles Nutter in his post Rite, Rubinius, and Everything &mdash; I think he's right.  Evan is hard at work making things work better in rubinius.  He's now got continuations working (I think this makes him the first alternative implementation of Ruby to do so), and says he should have serializable continuations soon (see his post on it here).  W00t!
347638
In a new post on his blog, Kore Nordmann takes a look at a feature that's been around a long time (first introduced in a message board application) - BBCodes.   The discussion on my blog post "Do not use regular expressions for parsing" ended in a discussion about BBcodes in general. I just used them as an example to demonstrate why it it is impossible to parse such a language with regular expressions - and mentioned in a subclause, that I don't see any sense in using them at all.   He looks at some of the myths surrounding them and their use (more secure, easier to use, safer than HTML) and gives some reasons for making teh choice of HTML over them.
449834
Sebastian Bergmann has posted the results of some benchmarking on the compilation he's done on the branches of PHP from version 3.0 all the way up to 5.3-CVS.   As people keep asking me for an update to my previous benchmarks (PHP / GCC / ICC Benchmark, PHP 5.1 / GCC Benchmark (Update), and PHP 5.1 Performance, I quickly ran a new benchmark today.   He rendered the results out into a series of charts defining the number of total seconds taken for the compile and how long each of the components took. It's impressive to see how much of a jump there was between the 3.0 series and 4.3.   He also includes his compile settings (and machine information) as well as the numbers for the results if you'd like to graph them out yourself.
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!