the morning paper a random walk through Computer Science research, by Adrian Colyer Made delightfully fast by strattic To type or not to type: quantifying detectable bugs in JavaScript Gao et al., ICSE 2017 This is a terrific piece of work with immediate practical applications for many project teams. Is it worth the extra effort to add static type annotations to a JavaScript project? Should I use
Almin 0.12をリリースしました。 Release Almin 0.12 · almin/almin StoreとStoreGroupが書き直されたので色々変わっていますが、マイグレーションツールでアップデートできます。 変更点 StoreGroupを書き直した Before: class AStore extends Store { getState() { return {a : "a value"}; } } class BStore extends Store { getState() { return {b : "b value"}; } } const aStore = new AStore(); const bStore = new BStore(); const storeGroup = new StoreGroup( aStore, bStore ]); conso
30000 lines of client-side JavaScript. No tests. Two difficult TV deployment platforms with poor tooling. Strong dependencies on poorly documented
Type Systems for JavaScript Oliver Zeigermann / @DJCordhose http://djcordhose.github.io/flow-vs-typescript/2016_hhjs.html Most recent version including TypeScript 2.0 can be found here (might be work in progress): http://djcordhose.github.io/flow-vs-typescript/flow-typescript-2.html Part I: Introduction Why using type systems? IMHO type systems make code easier to maintain type annotations can mak
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く