The case for setImmediate() - Human Who Codes
Posted at July 9, 2013 by Nicholas C. Zakas Tags: Performance, process.nextTick, setImmediate, setTimeout One of my favorite new APIs that has been beaten about is setImmediate(). While I’ll concede the naming is completely wrong, the functionality is completely awesome. The basic idea is to tell the browser that you want some JavaScript code executed after the last UI task in the event loop compl
Luvit.io
Familiar API Luvit implements the same APIs as Node.js, but in Lua! This helps teams migrate without having to learn a new way of programming. Async Choice Choose your async model; we don’t mind; we encourage experimentation. If you don’t like callbacks and event emitters, use coroutines and write blocking style code without actually blocking your event loop! Modular Core The various projects in t
ControlJS part 1: async loading | High Performance Web Sites
December 15, 2010 10:45 pm | 30 Comments This is the first of three blog posts about ControlJS – a JavaScript module for making scripts load faster. The three blog posts describe how ControlJS is used for async loading, delayed execution, and overriding document.write. The #1 performance best practice I’ve been evangelizing over the past year is progressive enhancement: deliver the page as HTML so
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Advanced async/await in Python 3.5
GitHub - caolan/async: Async utilities for node and the browser
