Windows PP 2005

eWeeks has a good coverage on XP Reloaded.  According to the articles, Longhorn is going to be delayed even longer and Microsoft is thinking about an interim release.  I think it makes sense although I think it should be called Windows PP, a quick relief.  That would make Longhorn #2 in the restroom metaphor.

What features should Windows PP have?  Here is my list:

  1. News reader fully integrated with Outlook, IM and WMP.
  2. Blogging support inside IE and Office.
  3. Built-in open P2P client.
  4. .NET 2.0

That's it.

Windows PP Take A Leak at a Store Near You!

What do we get with PUT/DELETE?

I asked this question in response to proponents of HTTP PUT and DELETE verbs disputing the points made by Russell Beattie in his Hypocrisy: RDF and the Atom API post.

So exactly what do we get in return for doing all this? Using PUT/DELETE is designing for the future? All that does is replace four characters ('POST') at the head of a HTTP request with other characters ('PUT' or 'DELETE') which could have just as well been within the payload or headers.

What tangible rewards do we get for:

1. abandoning support for millions of J2ME cellphones already out there.

2. forcing us to wait until there are enough Atom-capable J2ME phones out there

3. require everyone to support both REST and SOAP?

What do we get in return?

A sensible question, I thought.  I was hoping that my question would help them see the issue more clearly.  No such luck.  Ken MacLeod answered on the atom-syntax mailing list:

Off the top of my head, we get:

* more software that uses standards-level features in ways they are
   supposed to be used

* bug reports against tools and libraries that aren't implementing

* network effect with other tools, libraries, applications and
   standards that already use these features in the same way

* raising people's awareness to the fact that an X/HTML editor
   "saving" its content via PUT, as _many_ do, is just as good as
   PUTting an Atom entry

* protocol compatibility (PUT/DELETE => FTP's STOR/DELE)

* an obvious pattern for application-specific extension

* API extensions with at least one less dimension of lock-in

As I suspected, I am fighting up-hill against gnomes on Mount Nevermind.  In case you are not a fan of Dragonlance, Mount Nevermind is:

A Great, Huge, Tall Mound Made of Several Different Strata of Rock of Which We Have Identified Granite, Obsidian, Quartz With Traces of Other Rock We Are Still Working On, That Has Its Own Internal Heating System Which We Are Studying In Order to Copy Some Day That Heats Up the Rock to Temperatures That Convert It Into Both Liquid and Gaseous States Which Occasionally Come to the Surface and Flow Down the Side of the Great, Huge Tall Mound…

Sorry, Ken.  I know you are a smart guy but I think you are being oblivious to common sense on this issue.

Wise fragger Tim Bray lobbed his wisdom into the fray:

In your list, I do not observe any entries that amount to "this will make it easier to implement" or "this will enable features that would not otherwise be possible." Thus you are missing the two most powerful engineering arguments are are facing an up-hill struggle. In fact, it is observable that insisting on PUT & DELETE in fact adds to the difficulty of implementation in some contexts; which seems fatal to me when the arguments in favor are so philosophical.

To which Sam Ruby replied:

Do the words of somebody who has actually implemented this count for anything?

Ben Trott has implemented both too, would it help if he were to weigh in:"

Sam, words of implementors are good but Ben's experience is limited to the server-side.  Their words and words of others such as J2ME client developers should be used as weights on a balance and not as shields to protect wrong decisions with.  Besides, taking Ben's word of the issue is like using a yogi's word to design a bed.

BTW, I have just joined the atom-syntax mailing list.  It looks like a hot bed of activities.  Ken's post sparked off a long thread of discussion which you might want to follow.

Iranians Love My Blog

Hottest news this morning:

TEHRAN, Iran – Pentagon (newsweb sites) and Pakistani officials on Saturday denied an Iranian state radio report that Osama bin Laden (newsweb sites) was captured in Pakistan's border region with Afghanistan (newsweb sites) "a long time ago."

The director of Iran radio's Pashtun service, Asheq Hossein, said he had two sources for the report. The radio quoted its reporter as saying bin Laden had been in custody for a period of time, but a U.S. announcement of the capture was being withheld by President Bush (newsweb sites) until closer to the November election.

"Osama bin Laden has been arrested a long time ago, but Bush is intending to use it for propaganda maneuvering in the presidential election," he said.

Somebody over there must have read my Bin Laden's Capture and the Election post from two days ago and spread the meme.  Muhahaha!

News that makes me SMILe

Sorry about the goofy title.  I somehow got sidetracked this morning into tinkering with Java2D animation inside a SWT application and ended up reading the SMIL 2.0 spec.  Trail of thoughts from my Alternate News Reader UIs post stoked back into life along the way, this time focusing on scrolling.

Scrolling tend to interferes with reading because it is unnatural.  Scrolling amounts to keeping your eye focused on one spot of a book and moving the book around to read it.  As the book moves, your eyes defocus momentarily which is highly irritating.  If you haven't noticed it before, try it now.  Note that focus is maintained when eyes are moved instead.

What's really funny is that web browsers depend heavily on scrolling.  One way to remove or, at least, reduce amount of scrolling is to scroll in time instead of scrolling in space.  SMIL is, in effect, an XML standard for scrolling a document in time.  What does this mean for RSS?  How about playing RSS feeds on SMIL browsers by transforming RSS feeds into SMIL streams?

Proliferation of Blog Crawlers

The traffic to my blog has doubled in the past two months.  While some of that is due to new readers and subscribers, good part of that traffic is due to blog crawlers.  With the smell of money in the air, I am afraid we'll be seeing an explosion of blog crawlers in the near future.

How long before only a tiny fraction of the traffic is actually read by a person?  How long before the blogosphere is swamped by convenience-driven waste and greed-driven abuse?

Rediscovering Edward Tufte

My thanks goes to Scott Loftesness for his post which helped me rediscover Edward Tufte's wonderful site.  I have Edward's first book which is great but the pages in the Ask E.T. and E.T. Writings sections are even better IMHO.

Beside the preview of Sparklines chapter — a must read, sparklines are basically micrographs which are small enough to be inlined with text, stacked (piled?) for glance-sized pattern analysis, or embedded within another chart – from his upcoming book Beautiful Evidence, I liked this part of his comments about Gantt chart:

The chart might be retrospective as well as prospective. That is, the chart should show actualdates of achieved goals, evidence which will continuously reinforce a reality principle on the mythical future dates of goal achievement.

Reinforce is a big word in UI.  I liked his alternate design as well although I would have used a more color since I think more in terms of computer screens and interaction models instead of print.

A Note to Edward Tufte: Cheaper, normal size edition of your books would be nice.  Web versions would be even better but I guess I am asking for too much.