Man, @yoshuawuyts & co. have done an awesome job with the Choo Framework, way easier to grok than React, Redux etc. Way easier...
-
-
Replying to @niall_obrien @yoshuawuyts
Much closer to the javascript and node metal
1 reply 0 retweets 0 likes -
Replying to @jp10k @yoshuawuyts
Yeah, that's what I'm really liking about it. Anyone done something like Next.js with it yet?
2 replies 0 retweets 1 like -
-
Replying to @jp10k @niall_obrien
I wonder how that'd work - intuitively I think it'd just be a pattern, but perhaps I don't understand yet how the saga stuff works.
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @niall_obrien
Sagas provide a space to isolate async stuff, keeping side effects in a controlled place
1 reply 0 retweets 0 likes -
Replying to @jp10k @niall_obrien
I've read up on how sagas work, and the same can be achieved by choo's event emitters - very similar, just no need for generators and stuff
1 reply 0 retweets 0 likes -
In https://github.com/sotojuan/saga-login-flow/blob/master/app/sagas/index.js … 'yield take' would be 'emitter.listen()', and 'yield put()' would be 'emitter.emit()' - maps quite well :D
1 reply 0 retweets 0 likes
Err, I meant emitter.on() - emitter.listen() is not a thing haha 
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.