Skip to content
This repository has been archived by the owner on Mar 25, 2018. It is now read-only.

docs: Document the Event Loop as it Relates to Node #74

Closed
DavidTPate opened this issue Feb 3, 2016 · 5 comments
Closed

docs: Document the Event Loop as it Relates to Node #74

DavidTPate opened this issue Feb 3, 2016 · 5 comments
Labels

Comments

@DavidTPate
Copy link

This came up in the roadmap with #70 and I volunteered to get some content put together. I've done some local presentations on it for the JS folks in my town. I really enjoyed a talk by Philip Roberts @ JSConf EU 2014 something like that could be made more Node-centric and distilled into some GIFs for a presentation to help illustrate it.

@jrit
Copy link

jrit commented Feb 4, 2016

I see this issue listed on the docs quarterly roadmap along with an overview of "blocking vs non-blocking" and was wondering how you plan to cover this topic without involving the other, and how one would talk about blocking without getting into how the event loop works? I ask just for the sake of planning the topics, I was considering trying to help out on the blocking topic.

@techjeffharris
Copy link

I started work on this about a week ago and would greatly appreciate feedback!

nodejs/node#4936

@techjeffharris
Copy link

@jrit I'm imagining the "Introduction to Node.js" document introducing the concept of blocking vs non-blocking breifly (and pointing to the topic/guide for that) just before also briefly describing the event loop (and pointing to the topic for that). But that's just off the top of my head.

The trick I think is establishing a progressive hierarchy of documents: at the foundation we have the documents for those totally new to node which introduce but skim over many of the core concepts while providing inline links to documents of further detail.

Also, FYI - Just pushed updates to nodejs/node#4936

@DavidTPate
Copy link
Author

@techjeffharris That definitely sounds good, establishing a hierarchy of documents to progressively explain more I think would be the best. I'll take a look at your PR and provide any feedback I can.

@Trott
Copy link
Member

Trott commented Mar 13, 2018

Closing as this repository is dormant and likely to be archived soon. If this is still an issue, feel free to open it as an issue on the main node repository.

@Trott Trott closed this as completed Mar 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants