Status of setImmediate development about promises-spec

[briancavalier]

@juandopazo No worries. A mailing list is probably a good idea.

Yeah, seems like we, the Promises/A+ organization, should petition for standardizing an efficient next-tick, whether it's the current setImmediate proposal, or some tweaked version, or something else.

[ForbesLindesay]

👍 for us pushing for an efficient next-tick

I know it may seem a little weird, but I'm a huge fan of "issues" over "mailing lists". They're really easy to follow/not follow on a case by case basis. They support syntax highlighting. Virtually everyone involved has a GitHub account. I really wish ESDiscuss used GitHub issues rather than a mailing list because I can't afford to receive all the e-mails, but I'd love to be able to comment on/follow a few individual issues. Also, it makes it easy to see which discussions are on-going. For example this can be closed once either setImediate is implemented or we have agreed on our approach to the issue.

[unscriptable]

Good points, Forbes. The Promises/A+ development has been way easier for me to consume -- and participate in -- than most mailing lists.

[briancavalier]

Ok, maybe we stick with github issues until people feel there's a compelling need for another communication channel.

If anyone has thoughts on ways in which, and groups to whom we might start petitioning, please post here. I know several folks here are very involved in ES-discuss, CommonJS, etc etc, so maybe there are some inroads to garnering support and/or ideas there.

[kriskowal]

You are all welcome to join the Q-Continuum mailing list. As the name implies, it is not just about my Q, but the whole ecosystem. You’ll find a lot of interested parties are already there.

[ForbesLindesay]

I still always find myself wishing things were created as issues in the Q repo rather than being posted to that mailing list. With the exception of people who don't have a GitHub account, it's much easier and less spammy to have issues + a definitive point at which the discussion is considered "closed"

[domenic]

After filing this bug, I think we've done all we can. It's up to the browser vendors to prioritize. Closing, unless anyone's had any other brilliant ideas in the last month for pushing them to get going.

(Learn C++? Start submitting patches? ;))