3 ms·
Actually, a bunch of us are working on taking the pain out of async programming. Here's my approach, using (fab)'s chained continuations: http://www.flickr.com
by tr4nslator 16y ago
Actually, a bunch of us are working on taking the pain out of async programming. Here's my approach, using (fab)'s chained continuations:
http://www.flickr.com/photos/tr4nslator/4532445014/in/set-72157623883700702/ http://www.flickr.com/photos/tr4nslator/4532445014/in/set-72...
- swannodette 16y agoWhile this is cool, when you get to this point with JavaScript syntax why not just write your program in a Lisp like Clojure? People keep saying that JavaScript is good for asynchronous code, but that might not true at all. It's just that we JS hackers become very accustomed to a style of code that works great for simple user-driven events. In my experience this does not scale for much else. Maybe we can make it work, but I don't like what I've seen thus far. I want people to adopt a syntax that doesn't affect standard JS style: http://mootools.net/shell/q9ASd/28/ http://mootools.net/shell/q9ASd/28/
- tr4nslator 16y agoBecause I'd rather write my programs in a Lisp like Javascript?