Developers to Mr Jobs: tear down this wall!
583825
Apple faces calls to open iPhone Office 2.0 Conference Apple is facing fresh calls to open the iPhone as new evidence emerged of the technical and legal challenges developers face putting their software on the device.â¦
184873
Stop milking same old cow Advice from Microsoft on designing useful and uncomplicated software? Now, there's a novel idea.â¦
496932
A step-by-step summary of TechRepublic's project to take apart the Wii. Caution: This will seriously void your warranty.
532255
Elizabeth Smith has a new post to her blog today covering some of the fun she's been having with compiling things like Gtk+ and PHP-Gtk2.   So I've been using microsoft visual studio (actually it's Visual C++ Express, but uses the same stuff behind the scenes) to work on getting things compiled on windows. PHP-Gtk2 allows for some nifty extensions, well at least on linux. So I've been working to get versions of libglade, scintilla, gtksourceview and mozembed working on windows. It's a long, slow process. Here's the deal so far.   She talks about her current situation (what's compiling and what's not) and the software that she's trying to get up and running. She also mentions a problem she's been having with an error message talking about "unresolved external symbols" she'll need to track down (or get some help on - anyone out there seen it?)
387178
The Zend Developer Zone has posted the latest episode of their PHP Abstract podcast series with a focus this time on screen scraping (as recorded by Matthew Turland).   Matt has been building PHP applications since 2002. He joined the ranks of PHP-Oracle developers in 2006 when he became a programmer for METHODS Technology Solutions. He contributes to open source projects such as the Zend and Forkr frameworks. [...] We are going to veer off the beaten path today as Matthew talks to us about Screen Scraping.   You can download the mp3 directly or you can  to get this and the most recent episodes.
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!
371163
Since we launched at Web2  last week there has been a log of great feedback about Rojo .    First off is this *great* new Austin Power logo from Constantin Basturea   Smashing Baby!  On the subject of eye candy check out the CafePress store  that Chris  put together.  Very hip indeed!  I might get this for my girlfriend:  ... and this for my backpack:  We've been getting a lot of great feedback.  Thanks to everyone  for helping us out during our beta trial!  We even have our first Rojo external plugin :  "My room mate, Dylan Parker, has just released a plugin for FireFox named JustBlogIt. JustBlogIt is a Mozilla / Firefox extension that allows easy right-click posting to a weblog. It a ...
211888
Project failure 2.0 Remember when Java father James Gosling got flamed for uttering the ultimate Web 2.0 heresy: scripting languages aren't good enough for enterprises?â¦
394439
Popular posts from PHPDeveloper.org for the past week:PHPBuilder.com: AJAX and PHP Part 2 - XML Communication/ProcessingCommunity News: Zend Framework 1.0.0 ReleasedMike Potter's Blog: Slides for today's e-seminar on Flex and PHPBlogSecurity.net: Interview with Stefan Esser on WordPressCommunity News: India's First PHP UnconferencePro::PHP Podcast: Newscast for 2007.06.28JSLabs Blog:  How to create Microsoft Office Documents with PHPPEAR Blog: Request for ideas: New developer FAQPHP-Coding-Practices.com: Composing Methods: Split Temporary VariableRob Allen's Blog: Spanish versions too!
258314
Dare Obasanjo works at Microsoft.  In his blog post about the Yahoo layoffs, in a postscript, he indicates that Microsoft is interested in creating a Twitter clone.  I've said openly, on Twitter (and now here) that I would like to be part of a venture that aims to create a scalable Twitter. I've had several conversations with people who are attempting to do this. I haven't done a deal yet. My bet: There will be a lot of growth in Twitter in the coming years, and it seems likely that the Twitter company will not be able to scale their systems to meet the demand. There are features that should have been in the product and in the API months ago that are on the back-burner, likely due to Twitter's constant battle to meet meet demand (scaling). As a user, I'd like to view the product and the company as a black box, but that's impossible with the system glitches and outages. What users are doing now with Twitter is far more important, imho, than the servers, or the company. The company, understandably, thinks their issues are most important, but that's a matter of perspective. We don't own any stock in the company, so our perspective reflects that. To us, they're a utility. All this is a verbose way of saying that Microsoft applying their resources and scaling knowhow to this problem woud be an interesting development.
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.
403472
Reinhold Weber has put together a list of signs (40 in all on his "programming list of shame") that you're a lousy PHP programmer. Here's a sampling:   don't see the need and/or benefits of a good programming IDE like Zend Studio or Eclipse PDT have never used some form of version control like Subclipse don't use a consistent methodology don't use test-driven development don't return content but echo or print it from your functions or classes return HTML, not data, strings, or objects. don't allow intelligent error handling you think reusable software equals/requires your code to be OOP   Now granted, some of them are a bit more high level than others, but if you're not headed towards a lot of these, you might change paths, hop out of that comfort zone and branch out into the community and the language a little bit more.
692444
PHPEverywhere has a new posting today concerning a few criteria of a "great developer".
207972
Was the Novell/Microsoft deal a worthwhile well-meaning effort between renegade open-source geeks at Microsoft and geeks at Novell that got derailed by salespeople and management, after which it was turned into a nightmare deal with the devil?  I raise this question because I know someone with ties to people at both Microsoft and Novell.  He has a credible story to tell about what really happened, and how much it differs from what we now know about the Novell/Microsoft deal.  Unfortunately, I haven't been able to get him to write up the history - yet.  While I continue to pester him, here's the short version, third hand.
749231
When everything gets an API then everything you can imagine will be possible if you can write a script.  And sometimes, to give you an idea, all that has to happen is that a wall come down. The latest, most intriguing such wall was the paywall at the NY Times. Now all of a sudden we find the wealth of information published by the NY Times over many decades is available without tariff. More important, we can point into the archive. We've gotten so accustomed to the wall, that you actually have to think when it may be possible to go in there, as if it left behind a wall in our minds, even after the wall on the web is gone. For example, the first episode of Ken Burns's The War, an epic series about World War II from the American perspective, cited several NY Times articles. If you looked carefully you could see the dates, and the actual headlines, and then if you have a browser handy, as I do (I have an iPhone) you can actually read the article while the narrative continues. Today this is mostly a gimick, but I suspect as we get used to having history so available (like having a library microfilm machine, which I used to spend whole days playing with when I was a kid) it will change our sense of information, perhaps as much as anything else that's ever been on the web. Take movie reviews for example. What a thrill to be able to read a review of a movie that I love that came out in 1932! The reviewers back then were more forgiving, less sarcasting, more enthusiastic. Consider their review of the Hollywood Revue of 1929, a favorite of mine that I've only seen once (I'd pay for a DVD, if it were available). They loved audible movies (that's what they called them) as if the term "talkie" was as elusive as "podcast" was in the summer of 2004. Again, we've just scratched the surface. Wouldn't you like to have NY Times movie reviews integrated with Netflix? Or have Yahoo's movie rating service available on the NY Times site. And I have to wonder whether they really have gone all the way. You can't see the reviews unless you're logged in. Can Google's robots, therefore, see the movie reviews? Unless the've made some special arrangements, it seems not.  It would be helpful to get a technical guide to the newly hatched NY Times on the Web, or (as in the old days of software) a reviewer's guide, so we get some ideas of what to look at. Clearly a lot of work went into opening up the Times archive. I'm going to be in NY the week of October 8 and will have some time toward the end of the week. If anyone at the Times would be willing to spend some time with me reviewing what's now open, that would be helpful. In any case, at least the Times today is somewhat more available to be integrated into the fabric of the web. That's some progress. How much, remains to be seen. Postscript: Kottke did a great job of skimming the surface of the newly opened Times when it first came online, just one week ago today.
607777
Sometimes developers just don't think about how much trouble they'd cause with a rewrite of existing software. They think that moving up to the latest and greatest is the way to go, and that it makes perfect sense to say out with the old and in with the new. Aaron Wormus disagrees. Well, sometimes - it depends on the circumstances, really.   At ZendCon I talked about "Planning a PHP 4 to PHP 5 codebase rewrite, a practical approach". The talk was based on my own experience, as well as famous discussion of the topic such as Joel Spolsky's "Things you should never do" and the examination of "famous" platform rewrites.   Aaron gives an example of a large company making a move from a COBOL system out to C for a mission critical system. Based on his tale, they didn't put the thought needed into making this move - new development time, keeping old developers on staff, etc - besides the fact that customers don't like change and making a move to another platform is almost definitely going to be noticed by them.
62130
In response to a previous article from the Symfony blog, Paul Jones has pulled together some thoughts to some of the comments they made.   As the author of a relatively popular benchmarking article, I feel compelled to respond to this bit of misguided analysis from the Symfony camp about benchmarks.   Paul talks about the "straw-man arguments" presented in the Symfony article, including some references to Paul's previous benchmarks. He's even broken it down into a point-by-point response to make each point clear.