TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

What concurrency in Node.js could have been

5 pointsby erjiangalmost 11 years ago

3 comments

yortusalmost 11 years ago
Using asyncawait (<a href="https://github.com/yortus/asyncawait" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;yortus&#x2F;asyncawait</a>):<p><pre><code> var bakeCookies = async (function(cookie_mix) { print(&quot;Baking cookies...&quot;); var oven = new Oven(cookie_mix); var cookies = await (oven.bake(15)); &#x2F;&#x2F; bake for fifteen minutes cookies.decorate(); return cookies; }); </code></pre> It&#x27;s plain JavaScript, concurrent, and works with plain node.js, unlike StratifiedJS.
mattkreaalmost 11 years ago
So since it seems to me that this article entirely failed to mention why the callback pattern was harmful could someone else?
评论 #7990466 未加载
bjouhieralmost 11 years ago
The point about fibers is incorrect. I posted a detailed comment on your blog.