bryphe
bryphe
`brisk-gatsby` 😄 Cool idea!
Is this a general issue with `brisk-reconciler`? Or specific to `brisk`?
@kyldvs - API looks great to me! Thanks for sharing out the progress so far.
`trace` is mainly for debugging - it prints to `stderr` with the message + stack trace for convenience. Helpful when debugging, or if there is some corner case you hit...
> * I think I vote separate package in this case Makes sense. Baking it in seems be too opinionated - you could image `Rely-async` or `Rely-repromise` implementations perhaps too.
This sounds like a great approach! Thanks @cristianoc for the proposal and gist, and @jchavarri for implementing it 😄 Looking forward to it. I think this actually will solve a...
> This made me think that, if there was a common interface that exposed the type for a minimal, shared set of primitives, it could be possible to have 100%...
Cool, thanks for thinking about this @jchavarri & @cristianoc . The current model we have in this project doesn't sit right with me, just because it's _too easy to get...
> I played a bit with the "hooks carrying" solution, and one small downside is that it doesn't prevent users from not passing the hooks value around, in which case...
Thanks for the thorough and detailed proposal @jchavarri ! Those twitter conversations on hooks / type safety were really interesting. I suspect that perhaps the monadic / continuation models in...