Daniel P H Fox

I think I've changed my mind on the idea of consolidating `Eventual` with `Computed`. I think there is utility in cleaning separating yielding code away from non-yielding code in some...

A variant on solution 3 is by far the most promising to me. I think this is almost a perfect solution for the design requirements of both Fusion and this...

> I think it signals intent more clearly to put an explicit `become(firstValue)`, removing the first parameter from Eventual... The downside here is that calling `become()` is an optional action...

Sorry for the lack of response - I read the notification on my phone a couple days ago but never acted on it. I've been thinking about this though, and...

This construct is often referred to as a switch statement or a match statement, so I'll refer to this object as `Match` for brevity, and I'll also rename this suggestion...

I think we could go ahead with this if we were to switch Fusion to a lazy evaluation model :)

Related to #111

This is a difficult problem because, unlike frameworks like React, we have almost no abstractions for things like components by design. Components are a user-side coding pattern rather than a...

I personally use Fusion alone in my projects, but what you specifically use in your project is up to you - you know your project and requirements best :)

Some thoughts on Twitter about two approaches I came up with: https://twitter.com/Elttob_/status/1481782022712573964