You don’t know MobX State Tree | Max Gallo

You don’t know MobX State Tree | Max Gallo | iJS London 2018

Рет қаралды 11,281

Күн бұрын

Max Gallo (DAZN) | javascript-conference.com/spe...
International JavaScript Conference 2018 | javascript-conference.com/
Mobx State Tree is a simple and powerful solution to manage your application state, based on MobX. You probably heard about it and maybe you tested it out with an “hello world” project, but… are you using it in production ? Do you know how it scales and how to test it? DAZN is a sports streaming company with millions of users around the world, and just rewrote the entire front end of their website. At the core of their front end architecture they decided to use MobX and MobX State Tree. Max Gallo will explain why they made this decision and how it made their lives easier. Reactive Architecture, Model Composition, Mutability and Immutability are just a small subset of all the features that he's going to walk through in this session.
👍 Like us on Facebook | / javascriptcon
👉 Follow us on Twitter | / javascriptcon

Пікірлер: 17

@ToniLiem 5 жыл бұрын

idk why this video only have 1500+ view. It should get more since it explains MST in a very simple way. Thanks a lot!

@CoryMcaboy 5 жыл бұрын

I best explanation I have seen this far

@gendaria 4 жыл бұрын

awww thank you 😍

@ToniLiem 2 жыл бұрын

@@gendaria you are the one who switch me from redux to mst and its the best framework migration since reactjs. Thx a lot @max

@sivakrishna4270 Жыл бұрын

Very helpful. Thanks a lot!

@alfonsosebaq 4 жыл бұрын

congratulations, very good explanation

@edisondsouza3404 4 жыл бұрын

Great presentation. It helped me a lot. Thanks, Max!

@elephant_888 5 жыл бұрын

Great presentation! Much thanks!!

@irving99uk 5 жыл бұрын

Very well explained, thank you!

@aditsaxena979 5 жыл бұрын

Thanks for the presentation

@zealous.y 5 жыл бұрын

I think the differences presented here between one root store ("to rule them all"), injecting stores into other stores, and store composition are merely semantic: In all three cases, one store knows and uses other stores. The first example is completely explicit, the other two are a bit more confusing as the props/views/actions from other stores aren’t declared in the store that uses them. What do you think would be the advantage of composing/injecting into "big" stores over explicitly having them as properties in one big store?

@protonforest6431 4 жыл бұрын

Thank you!

@khumarmardanova 4 жыл бұрын

Thank you for explaining MobX

@zzej 4 жыл бұрын

Great video. The presentation could be better. For example when referencing code snippets in your talk you could've highlighted the portion of the code you where referring to. I was finding myself scanning the code just to find the part relevant to what you was discussing.

@gendaria 4 жыл бұрын

Thank you for the feedback!