Ugh, TIL JS now has a cute lil abstractions called Iterator. What is it? You can only access it using ES6 for...of - dammit language peeps
-
-
Replying to @yoshuawuyts
Iterators work excellently in languages like Rust, but don't come barging into JS and overriding things like Arrays - they are fine yknow
2 replies 0 retweets 0 likes -
-
Replying to @TatumCreative
thanks! - I won't be using it though, as spread introduces more bugs than it solves minus helping with the broken browser api
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @TatumCreative
though - I'm sitting here in Tokyo cursing at the people that came up with this tower of wonky abstractions1 reply 0 retweets 0 likes -
-
Replying to @TatumCreative
used them in conjunction with co which was cool, but in reality .next() could've been a convention, no need to add to lang
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @TatumCreative
"but async / await" - no fuck that too, examples never show error handling and I for one can do without nested try...catch
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts
I haven't dug into it. So far with our flavor of co, there isn't an easy error handling right away that I've seen.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative
yeah; so far I'm leaning towards using a combination of require('async') and streams - either Node core or pull-stream
1 reply 0 retweets 0 likes
stopped using co() once they became Promise based, for the sole reason that error handling went from meh to worse
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.