Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 1
    How wrote that? The asynchronous I/O is, as far as I know, a node-specific extension (though it does use a pure JS interface). Commented Apr 9, 2012 at 16:35
  • 1
    The language doesn't provide non-blocking IO. Certain frameworks do, however. Commented Apr 9, 2012 at 16:36
  • Can you provide the document you read? Maybe they meant language syntax and semantics provides for non-blocking IO. Commented Apr 9, 2012 at 16:37
  • 2
    @Cameron - I slightly disagree, some languages will aid you in implementing non-blocking IO while others will fight you at every turn. Commented Apr 9, 2012 at 16:39
  • 3
    @ChaosPandion: Very true! But there's no mention of async I/O in the JS spec, as far as I know. Commented Apr 9, 2012 at 16:43