5 ms·
It is virtually impossible to go back to a non unidirectional ui without feeling gross and disgusted. Working on a major angular project after doing some cljs
by smrtinsert 11y ago
It is virtually impossible to go back to a non unidirectional ui without feeling gross and disgusted. Working on a major angular project after doing some cljs with react feels like a decades step back - back to a horrible jsf like two way data binding disaster. Where is my state? Where is my api? Why did x put y here?
If it doesn't take hold this generation, it will definitely cycle back decades from now as the dominant way to structure ui code.
Between unidirectional flows and observables (or maybe some other async primitive) UI is getting very interesting these days. Personally I prefer rx to core.async. Core async just looks too awkward and low-level for me. RX I got immediately - a promise for a stream. Great stuff.
- sehr 11y agoHave you messed with Cycle.js? They just hit 1.0 recently and use rx extensively, it's an absolute blast to use
- smrtinsert 11y agoIt's number one my list of projects to check out! Looking forward to it.
- KurtMueller 11y agoAre you using this in production? Or for a side project? How and where are you using it? Thanks for any info.
- sehr 11y agoJust on a couple of rinky dink side projects with babel & webpack! Nothing major
- jlu 11y agoand of course don't miss out cycle-react, which is based on rxjs and cycle.
- XorNot 11y agoClicked through to this, spent a bit of time going huh? But it very gradually started to come into focus. I definitely going to give it a whirl for a few small in house webapps - thanks!
- scotty79 11y ago> Working on a major angular project after doing some cljs with react feels like a decades step back It looked for me that way even before I started learning about React.