A modular streaming web framework for Javascript.
- Tweets 103
- Following 0
- Followers 361
- Likes 0
@BlessYahu yes, since (fab) is just a library, you can access everything you'd be able to access otherwise.
Now playing: @jedschmidt's (fab) presentation at #jsconf: http://jsconf.blip.tv/file/3745736/
4
4
Regarding (fab) tersity/perf trade-offs, should the return callback for apps be passed as "this", or as an argument? http://bit.ly/bcruLD
(fab) is now on @izs's awesome npm, albeit parentheseslessly: npm install fab
Rumor has it that the legendary @creationix is releasing his #nodejs framework soon. Really looking forward to seeing what he's cooked up.
3
3
Sorry for the slow progress on the 0.5 branch! Turns out that building a dependency app that builds an app that builds apps is a bit hard...
1
Truly understanding how (fab) works is "a crucial step on the path to JavaScript enlightenment." (via @simonw at http://bit.ly/dhpE0P)
1
A few rewrites later, the core of the v0.5 branch is starting to congeal. Dependency management and other details here: http://bit.ly/aO5ija
Maybe the async JS community should embrace keming, and unify on `retum` as the standard callback name.
Awkward or clean? Another approach to (fab) styling, from @_ewr: http://gist.github.com/397399
Since async code is so functional and FP needs no 'this' keyword, (fab) is co-opting it for all callbacks: this( val ) is the new return val
Here's a summary of some of the changes happening in the upcoming version of (fab): http://gist.github.com/385361
2
Programming a Javascript library using "return" in only 1 location is as hard as writing with only 1 of this char: (!+[]+[])[!+[]+!+[]+!+[]]
Of course, the upcoming rewrite will also make (fab) more accessible for the parentheses-impaired: http://bit.ly/dyVWnL