WASH: What's it good for?

by Scott Elcomb Email

Most of the responses that I've had in response to the WASH post revolve around one question: What's it good for?

 

Believe it or not, that's a really hard question to answer. Almost as soon as jsConsole was created I discovered the question should be more like What isn't it good for?

The thing is that WASH is merely an extension to Javascript. Seriously. All it does is add runtime support to applications.

 

Some "real-world" examples might be:

  • Logging. Need a runtime bug report from your application?
  • 5GL Processing. Do you like how Office suites can interoperate between applications?
  • Prototyping. Like doing stuff on the fly?
  • Familiarity. Want to program for the web in ways that are familiar to standard "desktop application" development?
  • Ubiquity. Adds to virtually any Javascript library or browser based application.

 

Really, I don't know how to answer this question. When I gave the WAJAX talk at TLUG I was stumped by the question, "What's the killer app for Atomic OS?"

Quite frankly, I just don't know. The "pattern" (if you could call it such) is simply too flexible to describe.