Dave Johnson on open web technologies, social software and Java
1. There's zero ambiguity about single and double escaping, you can use whichever suits your publication process better and not worry about silent data loss. 2. You can include binary chunks right there in-feed, base64 encoded. 3. You get help for aggregate feeds using atom:origin 4. You have a date, atom:updated, with cleanly-specified semantics ("publisher says something changed") that's *guaranteed to be there* per-entry 5. It's in an XML namespace 6. It's got a good accessibility story: you have to have an atom:summary if there's no src= or it's binary. 7. You have clean semantics for linking to the entry this describes or the entry it's talking about. Personally, I think these are highly significant. But even if you disagreed, there are two other reasons why it would be good to get the Atom format spec finished: 1. Atom has an official specification change-controlled by a highly-independent standards org, there is no suspicion that any vendor or individual is pulling the strings. This might not strike you as important, but I assure you that there are lots of people to whom it is. 2. The atom format is one foundation of the Atom publishing protocol, and I guarantee that the world can *really* find a use for the protocol.
Tim Bray wonders why somebody would assert that blogs and wikis are converging because "in their essential nature, it seems like they couldn’t be more different."
Danny Ayers responds that "it’s not that they’re 'converging' it’s that they’re fundamentally the same kind of system."
My opinion? Blogs and wikis are similar in that they both aim to make it easy to "write the web" and as web systems, they both can benefit from many of the same technologies/features such as syndication, referers, trackbacks, WYSIWYG editors, etc. At the same time, they are different in essential nature, as Tim points out, but they differ in complementary ways -- and that's why they go so well together.
Blogs and wikis are merging. The evidence to support this assertion is the growing popularity of blikis or wikiblogs which include both blog and wiki capabilities. Some of these are wikis with blog features grafted on, some of them are blogs with wiki integration features, and some that are (or appear to be) designed from the ground up to be combined systems. Danny points out Bill Sietz's Wikilog and Martin Fowler's Bliki, but there are many more examples of combined wiki and blog systems.
BTW, I've written about this before.
The people of America have failed us today: "As Larry says, "It's over. Let it go." Jon is saying, "Don't complain - organize!" Although the previous post about the wacky voting system is interesting, it's unlikely that any sort of recount or technicality will change the fact that today, the people of the United States of America have voted for George Bush. It was close, but the Americans have chosen Bush. It's a sad day, but in a democracy, you get the politicians you deserve/vote for. This was their chance to change their leader and they have failed. For awhile, many of us thought that they had been conned into voting for Bush - that they didn't know he wanted to be a War President. Many people didn't equate the US policies with the people of America. We thought they had made a mistake. Now US policies = US Citizens. You Americans have my sympathies, but it's still your fault.
The Economist: Invading Iraq was not a mistake. Although the intelligence about Saddam's weapons of mass destruction has been shown to have been flimsy and, with hindsight, wrong [ . . . ] But changing the regime so incompetently was a huge mistake. By having far too few soldiers to provide security and by failing to pay Saddam's remnant army, a task that was always going to be long and hard has been made much, much harder. Such incompetence is no mere detail: thousands of Iraqis have died as a result and hundreds of American soldiers. The eventual success of the mission, while still possible, has been put in unnecessary jeopardy. So has America's reputation in the Islamic world, both for effectiveness and for moral probity.
Scott McConnell, American Conservative magazine: The record, from published administration memoirs and in-depth reporting, is one of an administration with a very small group of six or eight real decision-makers, who were set on war from the beginning and who took great pains to shut out arguments from professionals in the CIA and State Department and the U.S. armed forces that contradicted their rosy scenarios about easy victory.
Andrew Sullivan writing in New Republic magazine: The lack of stockpiles of weapons of mass destruction in Iraq remains one of the biggest blows to America's international credibility in a generation. The failure to anticipate an insurgency against the coalition remains one of the biggest military miscalculations since Vietnam. And the refusal to send more troops both at the beginning and throughout the occupation remains one of the most pig-headed acts of hubris since the McNamara era. I'm amazed that more war advocates aren't incensed by this mishandling of such critical matters. But even a Bush-supporter, like my friend, Christopher Hitchens, has termed it "near-impeachable" incompetence.And carefully consider this list of Republicans for Kerry in 2004 And this blog which documents Republican Swtichers which includes 42 newspapers (compared to 6 that switched the other way) And this collection of video ads featuring Real People who voted for George Bush in 2000, but will be voting for Kerry in 2004
Wiki hype soon to eclipse Blog hype?
Today Simon Brown pointed out a brief but interesting article he wrote called Blog Your Build. Simon wrote a couple of very cool little Ant tasks that make it possible for a build script to blog - to post messages to a weblog. Sounds crazy, but it is a really cool idea.
Build system blogging, newsfeed aggregators, newsfeed enabled source code control servers, newsfeed enabled issue trackers, blogs, and wikis make it possible to build a powerful dashboard website - a dashblog if you will - for a software development project.I imagine a development dashblog as a portal like site that looks a lot like Javablogs.com. The dashblog aggregates all of the project developer's blogs together into a project blog. Like Javablogs.com does, a dashblog might allow each reader to choose favorite blogs to be highlighted and those to be excluded from the main page. In the sidebars of the dashblog are displayed newsfeeds from the projects issue tracking system, the automatically generated build blog, the recent changes of the project's wiki, recent checkins to the projects source code control system, and news from other team's dashblogs.
Does your team already have a development dashblog?