I'm not clear what the issues with the Stream API are. Do we have a proposal for what would replace the API? The issues with the previous API where that clients of the API had to manage ownership of a field, and would likely mostly do that unsuccessfully.

@devoncarew : yes, I'm thinking about storing the callbacks as a list like addPostFrameCallback. @Hixie : does that sound good to you?

I'm also curious about the problems with streams? it doesn't seem too long ago that BLoC + stream was the go-to solution.. is there some major difference between framework use of streams, vs. framework users? I tend to follow the lead of the framework to have some uniform solution vs. having everything doing things differently (callbacks vs Listenable/ChangeNotifier vs stream).

@Hixie created another section in the style guide for this here: https://github.com/flutter/flutter/wiki/Style-guide-for-Flutter-repo#use-of-streams-in-flutter-framework-code

Streams are fine in general, they're just not the best solution to this problem.