News for hackers. Stuff that matters.
Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by CWIZO on Friday October 18, 2013 @10:06AM (#6571412)
You might need "nonFoods" sometime later but not right now at the start of the app. But instead of making 2 http requests you just make one, but use the thing you actually need as soon as it's available.

If you scroll the README file to the bottom you'll find some good use cases that explain it better than I just did :)

Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by sequoia on Friday October 18, 2013 @10:15AM (#6571454)
Yeah! There are more understandable examples further down. suggestion @joombar: since the first example is the first thing people see and it doesn't actually reflect the core usecase, perhaps add a note explaining that the example is contrived for simplicity's sake ~or~ make the primary example represent the core usecase more closely. Cool project!
Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by joombar on Friday October 18, 2013 @10:29AM (#6571543)
Hmmmm, yeah. Use cases doesn't take up much space, I'll put that before examples because it explains better what it is for.
Re:Oboe.js: reacting to Ajax/Rest quicker by not waiting for... by sequoia on Friday October 18, 2013 @12:46PM (#6572351)
OH yeah!! Those user-story style use cases really help clarify what it's for in a clear succinct way. Thank you!! (I wish all projects would do this)