Reactive, or not reactive: that is the question (Evgeny Borisov and Oleh Dokuka) [RU]
We all know the saying: “If all you have is hammer, everything looks like a nail”. In the world of software engineering it usually happens to the new, hyped technologies, which are not always used as they should be. As a result, we get more complex API which can only be supported by the engineers that went through fire and water, lots of bugs, and other problems.
How can we avoid broken fingers and things destroyed by hammer when we try to implement React?
As an example we’ll discuss a system with problems and, naturally, try to refactor it in reactive manner. We’ll cover benefits and drawbacks of not only the approach, but also API of specific implementations. We’ll evaluate the level of complexity before and after refactoring. We’ll try to learn what is joke and what isn’t.
1 view
542
178
5 months ago 00:01:12 1
What if the Strv 103 had ERA? | 125mm 3BM9 APFSDS vs S-Tank with ERA | Armour Penetration Simulation
5 months ago 00:05:02 1
MeshTools Sneak Peak – Project Objects and Splines onto Scene Geo, Release Update Coming Soon 2024.2
5 months ago 02:15:14 1
Dr. Matt Walker: Improve Sleep to Boost Mood & Emotional Regulation | Huberman Lab Guest Series
5 months ago 00:23:25 1
OM SAI NAMO NAMAHA MANTRA 108 Times SERIES Spirituality and Meditation
5 months ago 00:05:57 1
Rolling Method Red And Black Tie Dye T Shirt How To DIY