RxJS: destroy the state machine! - Stenver Jerkku / Front-Trends 2016

Learn our story how we discovered RxJS, how it helped to bring SaleMove from a massive state machine into an elegant event-based reactive platform. We started out with a big state machine that was difficult to maintain, test and develop. As the application grew we quickly saw that another approach was needed. After discovering RxJS, we quickly adopted the event-based reactive approach.
In this talk I am going to give you an overview of RxJS and why should you use it. I am going to talk about how once we adopted the event-based approach, it completely changed the way we think about state and state programming. All this with code examples.

[@wadenweh]

Where is the point about "destroy the statemachine"?

[@back2bikes336]

If you understand the implications of what Rx can do, then a finite state machine is to a large extent unnecesary. The last example where he is filtering clicks is basically a state machine in 3 lines of code

[@ikebipe]

@@back2bikes336 So it is a statemachine

[@deepfakescoverychannel6710]

@@back2bikes336 no. State machine func should receive new state and handle old state, for example finalize some resources for old state, and initialize for new state. It is impossible to do with RxCrutch

[@orlyffob8638]

A fantastic introduction to RxJS. Everything is a stream!

[@chriszhang3629]

Love this talk! I am just starting to learn RxJS and this talk helps me a lot!

[@VladyVeselinov]

5:00 "Your project manager is probably gonna get hyped when he sees this" hahaha :D

[@Icr125riderI]

Stenver that was great. Thanks!

[@pawel.badenski]

it sounds like he's saying "reactive brogramming" :)

[@KarjamP]

If his state machines really were difficult to maintain, test and develop, he wasn't practicing good development, to begin with. State machines are supposed to help with the control flaw, not destroy it! Sate machines are used whenever the need to keep track the change in input is needed within a system, or when a need to keep track of what it's doing becomes apparent. State machines co e in all sorts of sizes, from the AI within video games to even parsers of a programming language. Even the operating system of the computer itself happens to be one bug state mechine. If people were to find problems with using state machines, it's often because they were using state machines in inappopriate ways. These people are not entirely aware of what they're doing. For the record, RxJS is, itself, a variant on the state machine idea. Inputs are given to the system in the form of "events", with which the system may respond by putting itself into an altered state.

[@DanielNgo2014]

He didn't know what is a fsm.

[@dayvie9517]

RxJS subjects are stateful, you will never support states because that would mean working without data.

[@shirshzibbu330]

downvote. no mention of state machine or its destruction

[@ABDULSALAMAYINLA]

Scott please I'm tired !!! do you live in tree house now ?

[@behnamrasooli8801]

Did someone actually check the correctness of his talk before letting him go up the stage and mislead other developers? @7:37 "Event is fundamentally a collection?" What the F? You mean a stream of events is a collection, right?

[@frutiboy1]

this dude does not know what he speaks about

[@Hammerzeiterrrr]

why

[@thatoneuser8600]

@@Hammerzeiterrrr honzajde does not know what he speaks about