These are chat archives for jdubray/sam
so the distinction between schema and an instantiation of that schema that we call 'state' is useful
I am not an OO guy, I don't believe in classes / schemas (anymore). Actually that was the argument I had with the inventor of the MVC pattern at OOPSLA, I was presenting a paper called "extensible object models"
thank you. all corrected.
it's called state but it's stateless
S(M)for every view. That's why I "cache" it in a variable inside the model.
S = f(M)and then I pass this State forward. Is that "okay"?
Dan Abramov talks about how and why he wrote redux: https://devchat.tv/js-jabber/179-jsj-redux-and-react-with-dan-abramov
so sounds like a quick hack that turned out to be popular, and by chance (and/or brilliance) he did more than one thing right, and at the time guess he was just out of college, so not that experienced. but can't tell whether he's just humble or never really did some major research before settling down with the final design.
Yes. he is a bright kid no question about it. From what I have seen he tried to fix flux, so redux was designed as a better flux, he didn't start from scratch. You can't hack that space, you have to be a lot more deliberate in your analysis. TLA+ took 20 years to mature.
I do believe that React is brilliant, but they are reaching a point of insanity, who in their right mind would start building something on top of React.js+React.native+JSX+ Flux/Redux + Thunks + Saga + GraphQL + Relay? This is not engineering.