stardrive

8 ms·

1.
by stardrive 11y ago
Great series from Egghead! What can be said is that Cycle.js is indeed a new paradigm for JS. Anyone who has worked with other frameworks out there will know, that Cycle.js is cleaner, necessary and leading progress forward into the functio
2.
by stardrive 11y ago
Not sure if you've looked at Cycle Drivers, they are essentially services or plugins for side-effects. You manage them through sources and sinks and utilize them where every you like, as they run through dataflow components, very power
3.
by stardrive 11y ago
This is monumental! No other framework brings together dataflow and components like Cycle, those are just the facts making Cycle the premier state of the art framework in the JavaScript ecosystem.
4.
by stardrive 11y ago
RAD! Together with what @axefrog has in mind for tracing observable pipelines, a dash of Bret Victor and a bold Dan like initiative ( https://www.patreon.com/reactdx?ty=h ) DX can take a giant step to an unprecedented summit
5.
by stardrive 11y ago
What a fantastic overview of the past, present and future of UI flow and structure! There is a real need to step back and consider the available architectures and to build forward to a more natural and synergistic solution like Cycle.js.org
6.
by stardrive 11y ago
Except remember, RxJS is also a growing standard and the virtual-DOM Cycle.js uses has been tested to be a fair amount faster and robust than the one React has. Then there is also Cycle's Model-View-Intent pattern and leading edge work
7.
by stardrive 11y ago
Agree that those two benefits alone are super, may I also add: 3. The MVI framework, it's a great way to structure apps, much beyond the lifecycle methods React throws at ya. 4. The driver architecture, which shows forward thinking. It
8.
by stardrive 11y ago
Interesting to see what was meant to be the most glorious and final (to end all Flux wars) version of Flux get revamped with Rx: https://github.com/jas-chen/rx-redux
9.
by stardrive 11y ago
If you want to walk on the wild side and get out of the framework cage and take a breath in fresh air then checkout the following: https://github.com/channikhabra/yarr/blob/master/complete-tu...
10.
by stardrive 11y ago
Done, read on: https://medium.com/@andrestaltz/why-i-cannot-say-frp-but-i-j...
11.
by stardrive 11y ago
Okay, that explains a lot. It is also ironic because React's rejection of FRP in its completeness has also spawned a very poor substitute they call Flux. The number of Flux versions that have been churned out as a result is obscene. Th
12.
by stardrive 11y ago
Typo, meant to be turf, as in "React tried and abandoned..." or to toss aside without explaination. Title was getting long so turf had the edge to express the tweet.
13.
by stardrive 11y ago
LOL, to be even more correct, precise and specific the above should read front/event and back/data :)
14.
Why does React.js truf other innovations like Cycle.js?
6 points by stardrive 11y ago|9 comments
15.
by stardrive 12y ago
Hell yeah! Noticed opentype.js is merging in some of that new Path2D sass too. Lets just use the DOM for what its good for, the slower more form based aspects of an app. Then use canvas for what matters most and be done with it. IMHO state
16.
by stardrive 12y ago
Great to see HTML5 growing so rapidly during the past few years! That said, I'm not a huge fan of frameworks, they do not work so well except for basic pattern apps. When you have an app worth building you consider very carefully what
17.
by stardrive 12y ago
Come on people, HTML5 is winning! Another awesome and seemingly overlooked option here is ludei.com with their Cocoon platform, launcher and cloud build service. Put that together with React/Flux and some soon to be released Famous-Rea
18.
by stardrive 12y ago
Crazy to finally poke around the Famo.us University and then to read all these scalling comments. The scrolling did not work that well for me either, however having seen so many APIs for graphics in Java back in the RIA days until now, I th