Can't help but feel promises/async/await too primitive. Too many assumptions baked in. How many things could be parallelized but aren't?
-
-
Replying to @jlongster
That's why I like generators - not bound to promises and way less assumptions builtin
5 replies 4 retweets 20 likes -
Replying to @jlongster
I also like generators over async functions in JS more and more. That README though...
2 replies 0 retweets 2 likes -
Replying to @wycats @jlongster
"A ppx rewriter for monadic and applicative let bindings, match expressions, and if expressions." reminds me why I like the rust ecosystem
1 reply 0 retweets 3 likes -
Replying to @wycats
ppx's are bad, Reason can have this builtin, ignore that part. The rest? :shrug: I don't mind terms which are used correctly
1 reply 0 retweets 1 like -
Replying to @jlongster
It just places a barrier to entry that allows swamp castles to be built on jargon. Sometimes the noobs have the best insights.
2 replies 0 retweets 7 likes -
Replying to @wycats @jlongster
That kind of jargon turns me off immediately.
1 reply 0 retweets 7 likes -
Replying to @ryanflorence @jlongster
Strong confirm. You may love or hate Ember or Rust, but I enjoy working with people who treat accessibility as a first class goal.
4 replies 0 retweets 5 likes -
Those have jargon too. Does "resolver" mean anything to an Ember newbie? Hard to avoid jargon in technical fields.
1 reply 0 retweets 0 likes -
It's a piece of internal machinery for Glimmer. I'll take the hit, but this comparison is really off.
3 replies 0 retweets 1 like
To the extent that we talk about internal machinery in user facing features, I'm embarrassed.
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.