These are chat archives for jdubray/sam-examples
@bgusach Progressive rock band and then a programming rock band in the form of a software project, best of both worlds :smile:
I understand where you are coming from about not finding SAM the easiest think to understand. Myself I'm here because I have discovered a pattern myself and find them very useful in managing complex reactive flows.
For sure there is a real need for a pattern to emerge that supersedes the half-full boiler plate oriented narrow boxes that frameworks try to lure you into, until you discover that circles just will not fit into squares, much to your dismay and against all the hype.
For me the SAM acronym itself makes sense because state drives all actions which affect models. That's how it lines up with how I define and use control states anyways.
I think a nice top to bottom comparison table with one column per pattern/framework would be a helpful way to see the purpose of SAM. Just a succinct breakout of how different options handle the reactive loop and interact with the model, be it on the client or the backend.
Then after that is clear then various ways of wiring can be highlighted. Then finally code examples follow from that. The SAM pattern becomes lost in the shuffle so to speak if implemented in a specific wiring option before the comparison table is acturately presented.
This whole flow of revealing what SAM is follows a model (comparison table) then state (resulting wire options) then view (wired up code samples) format as well.