The Dave Scripting Challenge
Sun, 26 Aug 2001 11:20:47 -0700
With all due respect, you totally missed the point of AppleScript.
Look at the object model for controlling external apps.
These days the Internet is no further away from a script than an app was in
the early 90s.
Same concepts map. I like the man-page style external call. The REST
philosophy fully maps on the object model of AppleScript. You may not like
the way it does it, or you may (if you look) but that's where you're headed
if you like REST, imho.
----- Original Message -----
From: "Jeff Bone" <firstname.lastname@example.org>
To: "Dave Winer" <email@example.com>; <FoRK@xent.com>
Sent: Sunday, August 26, 2001 11:15 AM
Subject: The Dave Scripting Challenge
> Jeff Bone wrote:
> > Dave Winer wrote:
> > > >>What would a language or toolkit specifically for REST look like?
> > >
> > > Dude, I've already answered that question. ;->
> > >
> > > http://www.apple.com/applescript/
> > It was rhetorical, and no, I don't think that suffices.
> That wasn't meant as a swipe at Applescript; here's what I mean. I'm
> sitting here right now looking at Ethan Wilde's _Applescript for the
> Internet_ (circa System 8.5). I picked up a copy out of curiousity at a
> clearance sale a while back, I'll admit up front to never having done any
> Applescript since *way, way* back in the day. It seems that modern
> Applescript gives you some rather simple ways to publish a CGI handler
> and (conversely) fetch things from the Web.
> What it doesn't provide is a higher-level orchestration or coordination
> framework than you might expect from any language. You get the usual
> control flow things, assignment, and a reactive event framework to plug
> into. There's really no "compositional" metaphor for plugging Web
> services together beyond that... now, sure, that's sufficient for doing
> anything you might want to do. But it it a good fit, the same way the
> Unix shell is a good fit for dataflow programming? I wouldn't think