Struts: Watching the Paint Dry

Struts is a popular open source Java library from Jakarta Project, a subgroup of Apache Software Foundation.  Its popular enough that seven books have been written about it so far and knowledge of Struts is a common requirement for Java web application programmers.  Docuverse website was written using a beta version of Struts.  Its the beta part that annoys me.  Struts 1.1 has been in beta for over a year now.  Because Struts 1.1 has signficant advantages over 1.0.x, most of my collegues have been using beta versions of Struts 1.1.  Here is the history of Struts releases:

2001 Feb 23 – Struts 1.0-b1
2001 May 19 – Struts 1.0-b2
2001 Jun 02 – Struts 1.0-b3
2001 Jun 15 – Struts 1.0
2001 Nov 27 – Struts 1.0.1-rc1
2002 Feb 11 – Struts 1.0.2
2002 Mar 19 – Struts 1.1-b1
2002 Aug 12 – Struts 1.1-b2
2002 Dec 31 – Struts 1.1-b3
2002 Feb 23 – Struts 1.1-rc1

Now there is rumor of impending 1.1-rc2 release.  *sigh*  Struts team should do thousands of Java programmers a favor by switching to a different version number scheme like 1.1.{build#}.  If not, the animal on the cover of O'Reilly's Struts book should be changed from a strutting horse to a Sloth, world's slowest mammal.

LinkedIn via Blogland

Marc Canter is probably like the guy who saw the Bering land bridge form and yelled "Hey, guys!  Lets go across!"  He joined LinkedIn and invited 50 people.  I am too lazy to do that.  Its too much work to think about who I know, whether I should invite them, and to find and type in information.  LinkedIn should make it easier to invite.

One way to make it really easy to invite people is to leverage the informal network already formed in Blogland: blogrolls, links, trackbacks, and comments.  Given my blog's URL, a list of candidates for invitation should come up.  Even if some of them already joined, I want to know about it.  Best way to form new network is to add them in natural groups so they can support each other.  Come on Reid, this is no brainer.  Just swallow the whole Blogland a juicy cluster at a time!

A tip on subscription-based revenue model: make it free for and offer extra goodies to Connectors (as in Tipping Point).  This is how hunters catch whole herds.

LinkedIn

I just joined LinkedIn, a Ryze-like serviced founded by Reid Hoffman, former COO of Paypal.  What I can't figure out is the revenue model for companies like Ryze and LinkedIn.  I had a similar social network-based business idea for a while, but it was limited to specific industries and groups of people and had a per-project profit sharing.  LinkedIn and Ryze are more general so I don't know how peer-pressure for profit sharing can be applied here.

UPDATE: According to Joi Ito, Reid was not the COO of Paypal, but an EVP which I assume stands for Executive VP of something.  *shrug*  I still don't think there is any money to be made there.  In fact, I don't think there is anything of substance in so called social software.  Hype and rush will leave the market severely fragmented and no critical mass for anyone.  I maybe proven otherwise, but that is my view at this time.

Nature Conservancy Scam

Based on Washington Post articles (1, 2, 3, 4), The Nature Conservancy (TNC) smells like something that started with good intentions and then got swamped by carpet baggers.  Apparently, they interpreted the word "conserve" literally: to keep up and reserve for personal or special use.  Buying land using people's donation and then drilling for oil is ridiculous.  I'll bet Bush would be their dream CEO.

Their network of websites gives an entirely different picture, although I can't help notice that they look very well and expensively done.  I hope every one who took part in those "not illegal" deals get nailed to the wall.  I am going to tell everyone I know to avoid TNC like the plague.

Wiki Hype

People are looking at Wiki again, probably due to popularity of blogging.  My take on Wiki is that there are some good ideas in Wiki, but there are severe inherent weaknesses that usually leads to an ever growing pile of mess.

Peter Morville wrote about Trust by Design, a key component of Wiki, but fails to mention the downsides:

  • Difficulty of evolving Wiki content due to social and structural constraints
  • Inconsistent quality, style, and direction

If Blog is an one-mensional animal with a single continuous stream of consciousness, Wiki is a N-dimensional animals with many segmented strands of consciousness.  While the two are related on the surface, they are two very different beasts.

UI-wise, Wiki is like a fun house for cheery gully dwarves, endless interconnected rooms with five-feet high ceiling and no housemaids.  Think neck pains and perma-mess.

Radio Comment Dependability Problem

I use Radio and like it for the most part.  What I don't like is its tendency to depend too much on UserLand servers.  I don't mind generated pages with static resources from busy servers (i.e. W3C, UserLand), because I can replace them with my own copies.  What I am concerned about are dynamic contents pulled from UserLand servers, particularly the comments.

UserLand servers are usually dependable and speedy, but occasionally they are not available (like now).  When Radio comment service is down readers can't access the comments.  Once posted, comments are static content which can be stored locally as XML and HTML files as well as being embedded in RSS files.  Only the comment posting service need to be handled by UserLand servers since many Radio sites don't have CGI capabilities.

Confusing Myth with Mist

All too often, experts from all areas under-estimate the power of myths, thinking myths can be dispelled with information and education.  Myths are not mists, but memes more powerful than facts.  Even when people are informed or educated, myths persists still by interfering with memory and communication.  In my opinion, counter-myths are often more effective than truth.

I have no idea where this bit of thought came from.  Maybe this is just part of being an eccentric.

Thoughts on Slideshows and LIFE Magazine

I think people are overlooking a very important medium for communication: slideshows.  During the [second] Iraq war, I got used to looking at slideshows of the pictures from the war — I forget which online paper it was (either NY Times or Washington Post), but they don't have slideshows on the frontpage anymore, so I can't tell now.  Looking at those slideshows, reminded me of the feelings I had while flipping through LIFE magazine long time ago.  While words inform me, those pictures moved me.

Like Tim Bray's recent comparison between XML and sex, even a bad picture is still pretty good.  Piecing them together in sequence creates a magical moment, a cusp of me out of time and place.  An important factor is the size of the pictures.  they should be big.  How big, I am not too sure, but there seems to be a point where the edge of the picture becomes insignificant, a point of immersion.

In some way, I feel as though I am imagining things, but I really feel that there is magic here that will hit people harder than words can ever do.  It is something that moving pictures often fails to capture, because there is no space for me between the frames.  With slideshows, there is.

Regarding Permanence

[Following is my recent reply to a comment on importance of permance in newspaper UI.  I felt it deserved to be a post on its own.]

Regarding permanence, a particularly striking example is the way [we] remember articles in weekly or monthly magazines by the cover picture. Time, Scientific American, etc.  I still remember BYTE Smalltalk articles by the multicolored baloons on the cover. On the other hand, I am disturbed by the fact that I can't recollect individual issues of Playboy by the cover. <g> I think its because I was focusing mostly on the body and not the face. I haven't asked Time magazine editors about it, but I'll bet FACES make the most effective cover materials for 'memory-stamping'.

[this is newly added]

What I liked about Wall Street Journal is the way they frequently include copperplate-engaving style headshot pictures.  I think same thing came be done for bloggers.  Frankly, I never liked the 'shot from the bottom of Chinese takeout box'-style pictures popular among bloggers.

Latest on SARS Virus

According to this Washington Post story, SARS virus can:

  • live as long as 24 hours on plastic surfaces under room temperature
  • live as long as 4 days in diarrhea, 6 hours in normal feces, and 3 hours in baby feces.  Apparently acidity affects SARS virus.
  • remain viable indefinitely at 32 degrees

Common detergents have no effect on SARS.  No words on disinfectants.  I used one of those pocket-size disinfectant jells while at Toronto.  I have no idea if it was effective, but it was reassuring.  I did run into a nurse at a party though.  When she mentioned that she was a nurse, everyone sort of paused.  Now the good news:

  • SARS virus die at 98.6 degrees Fahrenheit and above.

Note that this doesn't mean you should bathe in boiling water, because doing that will just get you a hospital, a place you want to avoid when in a SARS zone.