Re: Imperative vs. Declarative programming

I think the key point is in this statement: "The execution doesn't 
go into Mozilla "core" (I mean the C++ code, the components that 
make up the real Mozilla) until there's some real work to be done. 
It's really fantastic."

in particular--"until there's some real work to be done".

So no, I don't think we've come full circle.  I like the idea of 
having workflows defined in a scripting language.  While I'm not 
using JavaScript with MyXaml (hmmm, maybe I really should take 
another look at this), I've put together a concept piece for 
managing workflows in XML.

See http://www.myxaml.com/wiki/ow.asp?Workflows

Marc

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xaml-talk/

<*> To unsubscribe from this group, send an email to:
    xaml-talk-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/