What do you feel about generators?
-
-
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
The stuff I'm working on lately... Sometimes JS seems like the wrong language.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative
whatcha working on? - I think JS is only great at prototypes / glue code - anything beyond that requires a lot of iteration
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
On Firefox devtools... memory, debugger, inspector, etc. All very async, lots of crazy inter-dependencies.
2 replies 0 retweets 0 likes -
Replying to @TatumCreative @yoshuawuyts
Lots of the code is written like we have a type system, but we don't have a type system, so it can be confusing.
1 reply 0 retweets 0 likes -
Replying to @TatumCreative
is this the "non-js people coming to js" style problem? - any chance you could push work down to some Rust layer? :/
1 reply 0 retweets 1 like -
Replying to @yoshuawuyts @TatumCreative
I feel like a lot of bad JS code is because of non-JS paradigms carrying over (like Enum). I was guilty too..
1 reply 0 retweets 2 likes -
like classes. Could do without those entirely...
1 reply 0 retweets 2 likes
Replying to @mattdesl @TatumCreative
haha, yeah - there's def a "JS people" vs "non JS people" culture; JS was my first lang ever so it's all natural
8:57 AM - 27 May 2016
0 replies
0 retweets
0 likes
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.