These are chat archives for jdubray/sam
Yes, looks like lenses are new again, have you seen:
@HighOnDrive we are in a situation where a) we start with the wrong factoring of the business logic and b) a bunch of people create libraries to make it less painful to adopt the wrong factoring... Sorry, I just don't see the light. I'd rather start with the correct factoring and use as few libraries/frameworks as I can. The flow to mutate application state is clear, there is no reason to warp it because you want to use the concept du jour:
I don't need any library to implement that flow. In some rare cases I may need a virtual-dom library in case my UI is very large and updates are very small (but in most cases this is way overkill)
The highlight of CycleConf are these slides, posting them here then sleeping for a bit. Nice to see state take it's rightful place in Cycle, even though most Cyclists don't care to see it this way:
Incidentally everything is a side effect, when you issue an intent, someone knows that the intent exists
do you think this formulation of actions is flawed, or just against the stated principles of architectures that use them (intents)?