-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with Observable without Observer: multicasting/Subjects #42
Comments
How do you feel about #41 (comment) ? Copying over: Hmm, I'm starting to like the original better:
Calling things generators or generator return results was super confusing, it took me at least a day to see @jhusain 's point about duality, it is beautiful but it will be very confusing for new users to see generators as both ends of the pipe. It took me a while to see he was doing this thing, it will likely take average users as long as me. I'm wondering if we can keep This sounds like the best of all worlds. It's much closer to the original design. I think that the return value of This has added benefits like |
Closing since we have Observer again. |
I realize Subject is not a party of this spec, but it is a part of the Observable ecosystem.
If there are no Observers, what is a Subject? How can a Subject subscribe to an Observable? I suppose it can be done with closures, but that sort of breaks Subject.
The text was updated successfully, but these errors were encountered: