These are chat archives for jdubray/sam
Hi @jdubray, hope you are well! I am trying the get my head around the SAM pattern once again, hence a few questions.
a.) Does the SAM pattern promises less boilerplate code than Redux? I guess not, right?
b.) I wonder why the function present(proposal) isn't simply called propose(proposal). Is it because of "present state" with a "proposal for new state"?
c.) What is a simple as possible real world use case scenario where I can demonstrate to myself the advantage of the SAM pattern, a use case which would be difficult to achieve or take more effort with Redux or MobX. There are many examples which show the pattern but IMO don't cleary show the advantage over the other patterns. Would that be a use case with some possible race conditions (for example between a user interaction and server response) or something that requires to handle multiple actions before updating the model, state and view?
Could it eventually be a use case like the flux challenge?
I could try the flux challenge with the SAM pattern and lit-html unless you have a better idea.