Top all-time · #8957
Neil Mix
Personal blog · neilmix.comprogrammingcareer
Neil Mix's personal blog at neilmix.com covers programming and career. Since 2007, 9 different Hacker News readers have linked it 10 times. No feed was found, so read it on the site itself.
Too few sampled comments (6) to say how often HN recommends it.?
Why HN links it
HN readers link Neil Mix's Narrative JavaScript documentation as a way to write blocking-style code for asynchronous callbacks. Commenters compare it with other JavaScript async tools.
Summarised by Claude from a sample of 6 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- /narrativejs/doc/6 people · 6 mentions · first linked 2009-02-02
What Hacker News says?
Try http://www.neilmix.com/narrativejs/doc/ -- "a small extension to the JavaScript language that enables blocking capabilities for asynchronous event callbacks".
Comment linking /narrativejs/doc/
on “Kal – a clean JavaScript alternative without callbacks”Submitted Solve the right problem as a story · 16 points
HN discussionSo instead of encouraging you to actually fix the bad nested callback code, you can dress it over with fancy syntax. Well done on making a whole language though. It's pretty challenging and I hope you do well. Aside: This seems very similar to narrativeJS in concept http://www.neilmix.com/narrativejs/doc/
Comment linking /narrativejs/doc/
on “Kal – a clean JavaScript alternative without callbacks”Submitted Software on the shelf as a story · 3 points
HN discussionI don't think this is true. Nodejs uses epoll/kqueue/select etc to multiplex access to multiple file descriptors from a single main thread. The async API is actually a price to pay (spaghettification). For example, the go language took a different approach: it created a cheap thread-like construct which doesn't incur in the biggest overhead of classical threading (namely pre-allocated linear stacks and context switc…
Comment linking /narrativejs/doc/
on “Vert.x (JVM async) vs Node.js Http benchmarks results”Submitted The Story Behind ES4 (the next Javascript) as a story · 2 points
HN discussionThere have been some different attempts to expand JavaScript syntax to make this style of programming more elegant. Narrative JavaScript http://www.neilmix.com/narrativejs/doc/ has a single construct, the arrow which turns everything after the arrow into a closure which is passed as an argument. StratifiedJS ( http://www.neilmix.com/narrativejs/doc/ ) is more rich with a number of new keywords: hold, spawn, wait etc…
Comment linking /narrativejs/doc/
on “I love async, but I can't code like this”Narcissus https://github.com/mozilla/narcissus/ It's been used as part of the Narrative JavaScript project to parse the JavaScript-like njs language and compile it back to JavaScript. http://www.neilmix.com/narrativejs/doc/
Comment linking /narrativejs/doc/
on “Javascript AST trickery with burrito”Neil Mix implements similar transformations in Javascript in Narrative JS: http://www.neilmix.com/narrativejs/doc/ . However, as I recall it aims more to provide some of the main benefits of continuations rather than a complete implementation of continuations on top of Javascript, which is more where I was trying to go with jwacs. Jwacs introduces very little new syntax to Javascript; I'm curious to hear which bits…
Comment linking /narrativejs/doc/
on “jwacs: Javascript With Advanced Continuation Support”