A collection of articles, ideas, and rambling from a guy who wrote some software that one time.

Friday, November 21, 2003

Client for What?

When doing something like browsing my email, what is it that I use a non-web-based client for?

  1. Native integration (such as drag'n'drop from a file manager, copy-paste of pictures from other applications, opening of local files)
  2. Responsiveness
  3. Keyboard Shortcuts

Beyond those requirements, it seems like a web browser can do almost anything required for any kind of text-mashing or abstract, logical application. There are apps like word processors which live or die based on performance of particular functions like turning fonts into pixels, but almost any communications-based application won't need to do something like that.

Will it?

2 comments:

nafai77 said...

Interesting thoughts; potentially almost anything useful could be implemented inside of a web-browser type environment. And, with something like nevow, I'm sure it makes writing a lot of those apps a lot easier. But! I'm not sure if I would like that. Webmail apps, for example, are great for getting at your mail if you don't have a machine of your own or your machine isn't currently hooked up to the Internet. But is there a cross-platform way of having a decent editor. Maybe it's because I am a member of the Church of Emacs, but I can barely stand typing in this text box here.

I'm not sure what I'm trying to say. If something like Livepage were to work reliably, perhaps I would reconsider. But much of what I have seen of browser-based applications I wouldn't use over a stand alone application any day. Then again, perhaps that is due to PHP.

moshez said...

Editors are perhaps the most popular non-issue raised.
This should really be fixed in browsers -- the ability to launch a browser from a text-box should really be more ubiquitus. Lynx has it, and it's an amazing feature. I'm using that feature right now so even though I'm posting to the web, I can use by beloved vi.