Image via Wikipedia

I got hooked on FriendFeed and wanted to create a different Web based interface. I wanted to be able to scan through several posts, open their links automatically, comment and “like” quickly, and have the list auto-update to show new posts. For some reason, I haven’t found a desktop client that I like (I tried Twhirl and AlertThingy). The clients are a pretty efficient way to comment (if you can find the right button), but I find notifications too disruptive, and neither client auto-opens links.

So, I created StumbleRead. Give it a try, and let me know what you think by commenting on this post (or below). Also, make sure you catch the hotkeys.

Disclaimer: Works best in Firefox, lightly tested in IE 7 and Safari.

Slowly but surely desktop software is being replaced with Web based software. The Web browser is becoming a platform for more complex software applications – the window through which you do everything – not just browse the Web. Web based software (coupled with “cloudcomputing”) has many advantages such as, automatic updates, portability from one operating system to another, and centralized data storage. It has traditionally had its downsides as well, like security, network speed, and user interaction.

As computers get faster, and internet connections more pervasive, Web based applications are becoming more practical. All Web browsers need are a few more features like local storage and support for working offline to make them a viable environment for 80% of all software. The remaining 20% will require specialized user interfaces or hardware that will probably never be fully “Web based”.

Several technologies have been invented to add these features. For a while, it looked like Rich Internet Applications (“RIAs”, see Silverlight and Adobe Air) would win out as the next application platform. However, recently I’m becoming more convinced that a combination of AJAX and browser add-ons will win.

Just 6 years ago it was conventional wisdom that (at least within Microsoft) Web browsers had become just as complicated as they would ever. I remember a Microsoft employ saying “their may not be another version of IE after 6, I mean what else is there to do?” AJAX applications were too slow to really replace destop applications.

In its early days, Javascript was a pain to write and debug. However, Javascript has matured. There are many libraries now exist to improve cross-browser compatibility and facilitate high level programming concepts. For example:

• Javascript is Object Oriented
• Firebug is a decent debugging tool.
• Namespace Hacks keep code clean
  
• JSON beats XML as a data transmission format
  
• Functions are first class objects
• Reflection (types can be inspected and modified at runtime)
• Decent development environments (code completion in Aptana)
• Threading hacks and event libraries
• Many advanced animation and UI libraries to choose from

Lastly,  Javascript (and JSON/XML) is an open standard that is not championed by any one particular company. This is not a technical advantage, but a cultural one. Javascript is pervasive and a safe (reluctant?) choice because it won’t be going away for a long time.

So, with these advances in mind, what exactly will the Javascript browser platform of the future look like? Here are the contenders:

• Firefox + Google Gears
• Safari (aka Webkit platform) with special features for client side storage and animation
• Internet Explorer + What?

Microsoft is in trouble for a couple reasons. I’m not sure if Silverlight is meant give code running in IE access to the Operating System. Even if it is, IE is only supported on Windows.

It may be a bit premature to predict the end of most desktop applications, but it sure seems like those who have switched operating systems will recognize and speed up the trend.

Appendix

see also Yahoo’s BrowserPlus