Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is this project dead? #50

Open
maxnordlund opened this issue Dec 13, 2015 · 9 comments
Open

Is this project dead? #50

maxnordlund opened this issue Dec 13, 2015 · 9 comments

Comments

@maxnordlund
Copy link

It seams like this hasn't been worked on in quite some time, ~10 months at the time of this writing, and I was just wondering if this project is to be considered dead?

If so, do you know any other project(s) which which provide similar features for node?

@osher
Copy link

osher commented Dec 30, 2015

if so - it would be a pitty :(
I woud like to help, if it matters

@gaurav21r
Copy link

I haven't dived much into this project, but with ES7's async many Async flow control projects are not needed anymore I think. Still, IMHO Strongloop should officially declare the status of this project. cc @piscisaureus @crandmck @kraman @sam-github

@sam-github
Copy link
Contributor

ES7 async/await in no way obviates this project. Its the opposite, await requires promise support for high-level control flow, and Zones is in some way is "a promisy encapusulation" of parts of the node.js loop life-cycle that will play quite well with await. That said, we haven't had much time to work on it. @osher what would you like to contribute? Keeping it alive is to a certain matter getting interested contributors. Its one of those "if everyone thinks its dead it will die" things, I think.

@piscisaureus
Copy link
Contributor

Dead for now.

Although I still believe that the underlying ideas and concepts are sound, the chosen implementation strategy (monkey-patching node.js core) proved to be not viable. Also scope creep and/or inflated expectations didn't help get the thing out the door.

There's still work going on in this area; tomorrow for example I'll be attending the node.js error handling "summit" in SF, and I hear a TC39 proposal for a similar concept (also called Zone) is under way.

@sam-github
Copy link
Contributor

OK, well, I take it back - don't try to resuscitate!

@piscisaureus will that "summit" be livecast?

@piscisaureus
Copy link
Contributor

More on the TC39 zones proposal:

The presentation is at https://docs.google.com/presentation/d/1H3E2ToJ8VHgZS8eS6bRv-vg5OksObj5wv6gyzJJwOK0/edit?usp=sharing and a more detailed proposal, although still a bit rough, is at https://gist.github.com/mhevery/63fdcdf7c65886051d55.

@piscisaureus
Copy link
Contributor

@piscisaureus will that "summit" be livecast?

Not that I'm aware of, but I'm sure the outcomes will be shared.

@doivosevic
Copy link

I think that this is the latest about zones:
https://domenic.github.io/zones/

@osher
Copy link

osher commented Apr 7, 2016

Well, I don't have anything speciffic in mind.

Basically, I'm a tech consultant, and I came accross a customer that built is infra around domains, and since this package is pending deprecation I've been looking for an alternative - so I happend to get here.
At the time I had capacity for new endavors, so I was probing with you to see how easily I could be engaged.

I'm more tight now, but am still interested.

The first point in contributing is, talk to the maintainers about the roadmap. so...
If somebody could brief me and direct me to the points help is needed - I can deliver ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants