Biff vs McFly

[coderdave]

So what's the difference between the two? Was Biff created simply so it can live under FormidableLabs? Will McFly continue to be maintained or is Biff now preferable?

[xpepermint]

+1

[kenwheeler]

BIff is set up a little bit differently. I wanted to create a fork of McFly where I could make changes without messing with the API for current users of McFly. McFly will continue to be updated and maintained.

The core differences are:

• Biff doesn't implicitly dispatch from action creators like McFly does. It requires users to explicitly call this.dispatch. This removes the need for action creators to return promise objects
• Biff adds async state helpers like pending and errors to keep track of the current state of a store, for things like async adds and optimistic updates.

[LongLiveCHIEF]

so are you thinking that biff will eventually merge back into McFly once some of the tinkerings have proven their value?

[kenwheeler]

Not super likely due to major API changes. If it happens though, it'll be a major version bump. That said, McFly will progress in its own trajectory, likely replacing promises with async/await, getting a higher order flux component, and managing events a bit differently.