Echo JS 0.11.0

<~>

tracker1 comments

tracker1 7 days ago. link 2 points
I'd love to see Node support some similar patterns... not sure what the locking risks are, or where information/scope may leak, but definitely cool... I also *really* like the async streams interfaces.
tracker1 10 days ago. link 1 point
The first, convoluted example should use `return cb(error)` instead of throwing.
tracker1 10 days ago. link 1 point
Conflates AngularJs and Angular (2+)... which is problematic considering they're very different beasts with component libraries that are incompatible.  I'd suspect the survey referenced also does similar.
tracker1 48 days ago. link 1 point
Can't access from work, at least one external resource is blocked, and not self contained enough to load on its' own.
tracker1 54 days ago. link 2 points
While not a bad article, I wish more people would just use the fetch (node-fetch, isomorphic-fetch) interface... I know some may be slightly easier, but in general fetch is good enough, and you can always create your own "client" that will abstract it's use a bit.
tracker1 65 days ago. link 1 point
I probably would have gone with node-fetch, but okay.
tracker1 69 days ago. link 2 points
Didn't look at the library page, but this would be cool if it works with generators for streams of records.
tracker1 69 days ago. link 1 point
Very cool... though I'd probably just jump to async functions considering it's requiring a super green browser for module support anyway.
tracker1 69 days ago. link 1 point
Very cool... The rate limit shouldn't be an issue since it's from the unauthenticated client, which allows one request per minute.  Combining with sessionStorage to only refresh if on the page for 3+ minutes could even be reasonable there.
[more]