Hi everyone,
I've created a simple library for asynchronous flow, based on specifying
dependencies. I implemented it using a dependency graph and LiveScript.
Except that it doesn't form one list of dependencies in order, it forms a
list of beginning and exit nodes, and executes everything in betwe
Can it handle loops?
On Wed, Jan 9, 2013 at 1:13 PM, Tom wrote:
> Hi everyone,
>
> I've created a simple library for asynchronous flow, based on specifying
> dependencies. I implemented it using a dependency graph and LiveScript.
> Except that it doesn't form one list of dependencies in order,
No, It's a Directed Acyclic Graph, but that's an interesting problem I'll
look into.
On Wed, Jan 9, 2013 at 10:16 PM, Mark Hahn wrote:
> Can it handle loops?
>
>
> On Wed, Jan 9, 2013 at 1:13 PM, Tom wrote:
>
>> Hi everyone,
>>
>> I've created a simple library for asynchronous flow, based on s
hi Tom,
did you come up with this concept independently?
It very much reminds me where I was with this concept 1.5 years ago.
Newer version is:
https://github.com/tatumizer/circuit
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Postin
I also tried this approach in the early days and handed off the code to
tmpvar as conductor. Personally it was too complex to be usable, but it
sure was a fun challenge to write.
On Wed, Jan 9, 2013 at 4:17 PM, Tatumizer wrote:
> hi Tom,
> did you come up with this concept independently?
> It
Oops, forgot the link. Here is the article announcing it from almost 3
years ago http://howtonode.org/step-of-conductor
On Wed, Jan 9, 2013 at 4:37 PM, Tim Caswell wrote:
> I also tried this approach in the early days and handed off the code to
> tmpvar as conductor. Personally it was too com
There's nothing wrong about it. The basic idea is quite natural :) No one
owns it. In a sense, it's a part of folklore.
The thing is: we have been discussing the same idea here ( just 4 items
below this thread) for entire month already.
And we discussed the previous one (mesh.js) here about 1.5 y
Oh right, I'm still on the hook for making a visual editor for this thing ;)
On Wed, Jan 9, 2013 at 3:38 PM, Tim Caswell wrote:
> Oops, forgot the link. Here is the article announcing it from almost 3
> years ago http://howtonode.org/step-of-conductor
>
>
> On Wed, Jan 9, 2013 at 4:37 PM, Tim C
I came up with same idea 25 years ago while writing simulations in queuing
theory. There was a language back then called Ratfor (Rational Fortran) - I
used it on Russian "version" of PDP-11.
I started learning javascript 2 years ago, and was surprised that this
simple idea is not in mainstream
there is no such thing as a new idea. Whenever you investigate patents the
harder you look the more you can go back in time.
On Wed, Jan 9, 2013 at 4:06 PM, Tatumizer wrote:
> I came up with same idea 25 years ago while writing simulations in queuing
> theory. There was a language back then ca
My async library has quite similar functionality and syntax. The goal was
to make it as short and simple as possible to use.
It has a very small API, but quite flexible.
https://github.com/tellnes/track.js
2013/1/9 Tom
> Hi everyone,
>
> I've created a simple library for asynchronous flow, ba
@Christian:
it suffers from the same disease as my old version of mesh.js.
Boilerplate, syntactic noise, no trees for the forest.
That's what I was told about my mesh.js. I looked at it again - and saw it
was true.
We have a lively discussion on circuit issue on github. Care to join?
There's only o
@Christian:
it suffers from the same disease as my old version of mesh.js.
Boilerplate, syntactic noise, no forest for the trees.
That's what I was told about my mesh.js. I looked at it again - and saw it
was true.
We have a lively discussion on circuit issue on github. Care to join?
There's only o
Sorry for double post. Don't know how to edit after I "send"
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this
2013/1/10 Alex Tatumizer
> it suffers from the same disease as my old version of mesh.js.
> Boilerplate, syntactic noise, no forest for the trees.
> That's what I was told about my mesh.js. I looked at it again - and saw it
> was true.
Thanks Alex for reviewing.
I can not see how I can change i
@Mark:
>there is no such thing as a new idea. Whenever you investigate patents
the harder you look the more you can go back in time.
Absolutely. And it's really weird. Maybe we all share some universal
consciousness, or something :)
Sometimes though people manage to combine 2 old ideas to get
16 matches
Mail list logo
