The battle of the mashup editors
137699
Blog: The big three tech companies all have their own mashup editors.  Who comes out on top?
481653
I'm back, with a very interesting topic too!  Joel Spolsky, ex-Microsoft Manager and software engineering guru has a new essay, How Microsoft Lost the API War that is creating quite a big storm in the blogging communitiy.  Joel posits that the priests in the holy Temple of Microsoft have lost their way, because it has split into two factions, and the wrong faction is winning. One faction worships on the alter of backward compatibility, while the other is led by fervent priests who are proselytizing to raise up the new gods of .NET and Longhorn. Joel suggests that the new gods will cause the destruction of the holy Temple because Microsoft's great victories were built on the altar of keeping customers happy with backward compatibility. Furthermore the old gods of the Windows API continue to grow more grotesque and cruel with the passing of time, driving former worshipers into the arms of the friendlier gods of World Wide Web.  This story sounds extremely plausible. I must admit that i fit the profile of the developer who used to develop on the Window's API, is familiar with COM and Win32 who now develops mostly using PHP and Python. However I continue to develop and maintain Windows apps that keep our customers happy, and we still plan to develop new Windows apps. Some points:  Temple of the Blind? Firstly, Microsoft is still a compelling place to work for to people who feel that they can make a difference. The Temple continues to attract talented people with a Unix background. For example we have the recent hiring of Ward Cunningham, author of the Wiki.  Microsoft is still able to keep talented people like Raymond Chen, and others like him who continue to look after the Windows API, and Longhorn apparently will still give high priority to backward compatibility. Open sourcerers like Miguel Icaza are sufficiently attracted to the .NET vision to stake their careers on Mono. Longhorn and .NET are compelling technologies, so even if Win32 is not so cute anymore, M'soft is providing something that remains very attractive.  What i do see M'soft doing wrong is that they aren't disseminating the .NET runtime fast enough. It remains an optional install in XP Service Pack 2 for example. Also their IE dev team appears to be hog-tied due to political reasons; nevertheless IE remains good enough, particularly when I can embed IE as an activeX control, something I cannot do with Mozilla (AFAIK) - Update: I'm wrong.  Temple of the Spider?  Secondly, people don't merely use a web browser. They run the web browser in the OS.  So let me ask you, if you are using DreamWeaver or HomeSite or Photoshop or vi or emacs or Gimp, how many of you are willing to give it up for a java applet (or whatever your favorite technology is) running in your web-browser? Precisely.  Temple of the Abandoned?  Third, Joel makes the claim that developers are not developing to the Windows API. Well he could be right. But I bet a lot of them are still calling Win32.  If you are using a framework or IDE like Delphi or wxWindows (or .NET or VB) then you certainly are insulated from the Windows API, but that doesn't mean that you're not calling the Windows API all the time. I don't see Borland dropping their Windows version of Delphi at any point in time.   In fact, the fact that many developers are using some form of framework is a compelling argument for Microsoft to enhance the .NET framework to attract developers who are using other frameworks.  Today, not that many students learn x86 assembler, but that doesn't mean that Intel lost the CPU wars. Just because fewer people are learning Win32 doesn't mean Microsoft has lost the API wars, if the frameworks run predominantly on Win32.  Temple of the Lost  Joel even warns you in the beginning that "because I'm talking about big trends, I need to exaggerate and generalize". But you still get sucked in because Joel Spolsky is a first-class writer, in the same order as Philip Greenspun or Eric Raymond. That makes him so persuasive and plausible. But this is not Indiana Jones and doomed temples, but Steve Jobs and reality distortion fields.  Other opinions:  Harry Fuecks (PHP is ASP's upgrade path),  Dennis Hamilton (M'soft is just covering all bases), Robert McLaws (Joel is wrong in 7 points), Oliver Travers (the web is not good enough), One Run-time to Rule them all....
377889
Plus: Mashups for the masses and HD video in a digital camera.
327265
Okay I've been writing about OPML reading lists here for years. I'm now on my second implementation, so maybe this time I'll get it right.  But there's something cool that happens when (hypothetically) the entire installed base of podcatchers supports OPML reading lists. All of a sudden the subscription problem goes poof! Ask anyone who's worked on a RSS reader, for that matter, ask anyone who's used one, what a PITA it is to subscribe to a feed. All those little buttons, or copying and pasting, and looking at urls, and trying to figure out whether you want this format or that format. It's a miracle anyone actually subscribes to feeds it's so damned complicated. Before you blame anyone, it's not actually anyone's fault. It's a result of the market not being a monopoly. The only way to solve the problem is if everyone uses the same web app to manage subscriptions. And we know that's not going to happen any time soon. Or, if every reader supports OPML reading lists. Now that might actually happen, even though it's not very likely. But podcasting, that's a whole other story. According to many people there's only one podcatcher, iTunes. So that's simplified the problem. For example, look at this page of NY Times podcasts, and how they handle it.   See the Subscribe button? Nice. Except for one thing. It really should say "Subscribe in iTunes" because that's what it does. And it works, because in many people's minds, iTunes is the only way to subscribe to a podcast. And it could stay that simple if Apple would do one thing, offer the option of publishing the OPML automatically to a publicly accessible web address, so the user could continue to use Apple's server to handle subscriptions, even if they're using a different podcatcher (for example one that runs on a Nokia N800). It would be the mark of a truly great company if they did that. Maybe they are that great. Otheriwse at some point we're going to ask the NY TImes to change their page. And they may not be too happy about that. Wouldn't blame them if they were. Moral of the story: If we can centralize the subscription process, and move it out of one reader or another, and get the readers to all support subscription to reading lists, the awful ugly issue will go away for users. It's one of the oldest tradeoffs in the tech business, to make it simple for users, the vendors have to give up some power.
737544
Over on Marco Tabini's Weblog today, there's a new posting that might hit close to home with quite a fe developers out there - a discussion on code documentation.
466712
The race for the best mash-up builder picks up as Microsoft opens up Popfly at the Web 2.0 Summit.
473809
On his blog today, Stoyan points out a topic he's started over on the OpenSourceCommunity.org site - What do you think makes a good CMS?.   This year's Packt Publishing awards for the best Open Source CMS are on their way, starting middle of July. I've been selected as a judge in the PHP CMS category. [...] How can one judge something as diverse and liquid as a CMS? Content management comes in all different shapes, some systems focus on solving some problems and they do a better job than another CMS that mainly tackles different types of problems.   He shares the experiences he's had with CMS and companies that have rolled their own in the past as well as a small list of things that he's thinking about making "the standard" for the CMSes to be judged by. Also included is a lengthy list of requirements that he sees that need to be included for any decent CMS to move to the next level.
572568
One's a PC brain, the other's a Mac-head--two PC World editors strongly disagree about owning this week's must-have gadget.
511332
The "free encyclopedia that anyone can edit" goes online. Doing research becomes easier but community editing means the information may be less credible.
661071
PÃ¡draic Brady continues his series looking at the creation of complex views in the Zend Framework with part six today all about gathering together the thoughts and ideas from the previous articles into a cohesive whole.   Part 6 now takes our previous fragments of theory and attempts to stitch them together into a cohesive whole - a description of a possible end solution. Yes, I know code talks loudly, and we'll get there with an almighty bang in Part 7 (which I promise is no more than a week away). Until then it's more verbosity.   He suggests a list of six terms to help get everyone on the same page when talking about the complex views:   Includes Partials Dispatches Layouts Placeholders Response Segments   Since these terms would mean nothing without proper definitions, he provides a few paragraphs on each explaining what they are and, where necessary, using code to illustrate the point.
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
27278
Excellent competition forced our editors to make some difficult decisions for the 2006 Editors&#39; Choice Awards for software, hardware and services.
588418
As new digital-distribution plans gain traction, an inevitable fight over publishing royalties breaks out. If songwriters lose, your ears will suffer. Commentary by Eliot Van Buskirk.
389639
There is an interesting post on OnLamp.com that mentions the search for a good wiki system. Read the post to find out why the author thinks that the wiki world "needs the kind of vision that will make the product more accessible, more polished, less prone to abandonment or neglect...", and the several comments that follow.
714863
What do you think of the new design?  For those of you reading via RSS just click on the permalink.   Fixed layout.  Blue background.  Nice clean sidebar.  No more obsolete links. Updated content.  All to give the appearance that I'm a professional!  This is part of my new effort to blog more now that I have Rojo  launched.  Anyway.  If anything looks strange please let me know!  I'll also be making some additional layout tweaks in the next couple of days.  In the meantime this will do...
369995
New .mobi and .jobs, a shift in the ownership of .net
404798
The International PHP Magazine is back this week with the results from their latest user poll that asked the question "Which Stage Comes First in the Development of the Basic CMS?"   Of course, of the options they gave, "Planning your CMS" came in with an overwhelming lead of 60.5 percent of the votes. Lagging far behind that was "Further Development" and "Database creation". It is good to see that a large majority of the people out there think that taking the time out to plan out the application first is the best way to go. Throwing something together, especially something that can get as complex as a CMS, is a very bad idea.   Be sure and get your votes in on this week's poll that asks which of the given options including "Web and command-line interface" and "Generates a todo list from @todo tags in source") wouldn't be a good option to be added to the phpDocumentor functionality.