-
Notifications
You must be signed in to change notification settings - Fork 1
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
UniRx and Unitask #1
Comments
Hello, Before I continue please note that I am using a translation tool to compose this response, so there might be some mistranslation. Thank you for your understanding. While UniTask and UniRx may seem similar at first glance, they serve different purposes. UniTask is intended for delaying the execution of methods until certain conditions are met. On the other hand, UniRx is focused on implementing the Reactive Programming paradigm with a Publish-Subscribe method, making it more suitable for 1:N correspondences. UniRx is a key tool for Reactive Programming, aiding in writing logic declaratively. In declarative programming, you only describe what needs to be done, and the details of when and how it is executed are handled internally. This approach is much more advantageous than imperative programming in terms of readability, reusability, independence, and maintainability. An important feature of UniRx is how it is composed entirely of pure functions, a concept mentioned in functional programming paradigms. This composition helps in reducing side effects, which is another significant advantage. Thank you. |
Thanks for the answer. Translation has no problem. I need to further inspect into unirx I guess. Thanks for the repo and detailed explanation again. |
Hey, thanks for making this example repo and writing a detailed explanation for it. It is really useful. I wonder what is essential about UniRx, it seems like Unitask can do most of the things unirx does with Asyncreactiveproperty. What extra Unirx has?
The text was updated successfully, but these errors were encountered: