I can't say. For use in widgets, there are already a number of mechanisms to help them deal easily and naturally with Futures. It depends on what other use cases might be envisioned, but the Future version would mean you wouldn't really have to explain the need to keep it away from the builder thread.

Also, I guess it depends on if the Future version was implemented in such a way that the work was done on another thread. If it is just a cover for doing asynchronous work on the same thread then we'd still potentially see some disruption of frame build times maybe?

Perhaps [USER] or [USER] might have some insights.