Skip to content

Update index.md #3992

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.

Sign up for GitHub

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

Merged
3 commits merged into from
Sep 8, 2021
Merged

Update index.md #3992

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e1334da
Update index.md
s-mrb Jul 20, 2021
c8a0ea7
Merge branch 'master' into patch-1
Sep 3, 2021
bcc7d92
Merge branch 'master' into patch-1
Sep 8, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions locale/en/about/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,9 @@ This is in contrast to today's more common concurrency model, in which OS thread
are employed. Thread-based networking is relatively inefficient and very
difficult to use. Furthermore, users of Node.js are free from worries of
dead-locking the process, since there are no locks. Almost no function in
Node.js directly performs I/O, so the process never blocks. Because nothing blocks, scalable systems are very reasonable to develop in Node.js.
Node.js directly performs I/O, so the process never blocks except when the I/O is performed using
synchronous methods of Node.js standard library. Because nothing blocks, scalable systems are very
reasonable to develop in Node.js.

If some of this language is unfamiliar, there is a full article on
[Blocking vs. Non-Blocking][].
Expand All @@ -41,12 +43,11 @@ If some of this language is unfamiliar, there is a full article on

Node.js is similar in design to, and influenced by, systems like Ruby's
[Event Machine][] and Python's [Twisted][]. Node.js takes the event model a bit
further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems, there is always a blocking call to start the
event-loop.
further. It presents an [event loop][] as a runtime construct instead of as a library. In other systems,
there is always a blocking call to start the event-loop.
Typically, behavior is defined through callbacks at the beginning of a script, and
at the end a server is started through a blocking call like
`EventMachine::run()`. In Node.js, there is no such start-the-event-loop call.
Node.js simply enters the event loop after executing the input script. Node.js
at the end a server is started through a blocking call like `EventMachine::run()`.
In Node.js, there is no such start-the-event-loop call. Node.js simply enters the event loop after executing the input script. Node.js
exits the event loop when there are no more callbacks to perform. This behavior
is like browser JavaScript — the event loop is hidden from the user.

Expand Down