Unification of The "Reactivator"08 Feb 2015
For last few year, i started to implemented the reactive programming into few of my projects with a different flavor like C#, ObjC, Swift and Java. From my experience in implementing the RP, its feel like filling the hole in your chest that already been there since the ancient beginning of the computer programming. There’s a thousand way that you can describe on the need to go reactive and why we need to embrace it.
The most prominent moment in RP is while using it in C#, from there i learn a lot on the fundamental of the RP, getting in-depth view of the core implementation of it and renewing the inner spirit of reactive programming. And i can say it’s does solve a lot of my programming problem, although it’s introduce a newer set of problem. But it’s make you code clean and more readable, reduced invisible spaghetti link and easier to maintain.
The only thing that i want to see in the near future is.. I hope that community of RP programmer, libs provider and implementer started to discuss on the unification and standardization of the RP implementation such using common term/keyword and jargon on the code level such ‘Observable’, ‘Subscriber’, ‘Producer’,’Signal’ and others, despite the limitation on some reserved keyword or core library for some programming language. By narrowing this different i think i will speed up, the adoption rate of the RP from one language to another language.
For newcomer to RP it’s time to make a move, be reactive and don’t forget to sign the manifesto at reactivemanifesto.org, there’s a plenty of increasing RP resources available out there, plus a hyper-reactive community to help in your journey, good luck..