@@ -53,12 +53,12 @@ synchronous methods of Node.js standard library. Because nothing blocks, scalabl
5353reasonable to develop in Node.js.
5454
5555If some of this language is unfamiliar, there is a full article on
56- [ Blocking vs. Non-Blocking] [ ] .
56+ [ Blocking vs. Non-Blocking] ( /learn/asynchronous-work/overview-of-blocking-vs-non-blocking ) .
5757
5858---
5959
6060Node.js is similar in design to, and influenced by, systems like Ruby's
61- [ Event Machine] [ ] and Python's [ Twisted] [ ] . Node.js takes the event model a bit
61+ [ Event Machine] ( https://github.com/eventmachine/eventmachine ) and Python's [ Twisted] ( https://twisted.org/ ) . Node.js takes the event model a bit
6262further. It presents an event loop as a runtime construct instead of as a library. In other systems,
6363there is always a blocking call to start the event-loop.
6464Typically, behavior is defined through callbacks at the beginning of a script, and
@@ -73,13 +73,7 @@ library or framework.
7373
7474Node.js being designed without threads doesn't mean you can't take
7575advantage of multiple cores in your environment. Child processes can be spawned
76- by using our [ ` child_process.fork() ` ] [ ] API, and are designed to be easy to
77- communicate with. Built upon that same interface is the [ ` cluster ` ] [ ] module,
76+ by using our [ ` child_process.fork() ` ] ( https://nodejs.org/api/child_process.html ) API, and are designed to be easy to
77+ communicate with. Built upon that same interface is the [ ` cluster ` ] ( https://nodejs.org/api/cluster.html ) module,
7878which allows you to share sockets between processes to enable load balancing
7979over your cores.
80-
81- [ blocking vs. non-blocking ] : /learn/asynchronous-work/overview-of-blocking-vs-non-blocking
82- [ `child_process.fork()` ] : https://nodejs.org/api/child_process.html
83- [ `cluster` ] : https://nodejs.org/api/cluster.html
84- [ event machine ] : https://github.com/eventmachine/eventmachine
85- [ twisted ] : https://twisted.org/
0 commit comments