@lynaghk precisely. The line between those two, like between view and model in oo, is the core design problem.
-
-
-
@asolove I love that Angular.js enforces all app state is kept in JS objects; the biggest downside is dirty-checking perf. And, er, JS. -
@lynaghk I've had a lot of trouble using core.async realistically without needing to break out of the sync nature of go blocks. Could be me. -
@asolove For UI stuff? You want to pair program on that topic sometime next week? -
@lynaghk yes absolutely. Have something in mind? -
@lynaghk I have some drag and drop stuff for sketchpad that might be good.
End of conversation
New conversation -
-
-
@lynaghk@stuartsierra core.async is a concurrency system, not a state management system. Go blocks should be mostly stateless.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
2/2
@lynaghk@stuartsierra@swannodette Maybe I've misunderstood his reasoning? core.async excellent for event passing though! -
@jarohen@lynaghk@stuartsierra yep, local loop state is not for observing -
@swannodette Thanks for clarifying - the pattern's just clicked :) I do like the 'trichotomic design' - fills a gap in my previous thinking!
End of conversation
New conversation -
-
-
1/2
@lynaghk@stuartsierra Even after@swannodette's excellent blogs, would still use data for essential (tar-pit style) state...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@lynaghk One of the reasons why I randomly rant about propagators and other "reified" cell approaches.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.