search

bigeasy / cadence

A Swiss Army asynchronous control flow function for JavaScript.
https://bigeasy.github.io/cadence
MIT License
35 stars 7 forks source link

Cadence general discussion. #1

Open bigeasy opened 12 years ago

bigeasy commented 12 years ago

Ask questions here.

bigeasy commented 12 years ago

Before this goes out, I need to be comfortable with the variable names.

Big one is $vargs versus $splat. The former is C sounding, but not what C actually calls them. The latter is Ruby sounding and comes to me from CoffeeScript.

bigeasy commented 12 years ago

Explicitly named context names passed to cadence appear to be on the way out.

bigeasy commented 12 years ago

I'm not going to add such a thing to Cadence, but I keep thinking about how to use Cadence to replace Bash scripts. What do I miss? Pipelines, redirection and globbing. What else do I miss?

Totally a separate project. You would have to have an answer for each of the core utils, plus diff.

demarius commented 11 years ago

What do we want the documentation to look like in preparation for this release?

bigeasy commented 11 years ago

You were doing great, actually. What probably needs to happen is we break up the documentation into steps, set an order for the steps, then go though them a step at a time. The documentation is already structured in this way.

As a first pass, it needs to simply take a stab at explaining each feature. Where I believe I can help is in designing first a good toy example for a property of Cadence, then a good real world example of a property of Cadence. Some of the current examples are toys, some are real world. We ought to have both for each step of the way.