RIP Redux: Dan Abramovich Announces Future-Fetcher

Post by cheez » Thu, Mar 01, 2018, 3:28 PM UTC

binocarlos wrote: post #25

I use redux a lot and love the way you can reason about the state of the app from a single object - which opens up all sorts of useful things like time-travel etc. However - after having plugged in a lot of reducers - the boilerplate code required to do simple stuff becomes a real bore. I've since compromised by using a simple `key-value store` reducer that I can write new values to without needing a new reducer with…

    interface FooState {
      myNumber: number;
      myArray: number[]
    }

    class Foo extends DataModelImpl implements 
    IDataModel {...}

    const foo:IDataModel = new Foo()
    foo.updateState(state => state.myNumber = 10)

    const callback = (num:number) => {...}
    const unsubscribe = foo.watch(state => state.myNumber,callback);

    ...

    unsubscribe()

Post by cheez » Thu, Mar 01, 2018, 6:37 PM UTC

rwbcxrz wrote: post #19

> The concepts are clear to those with a Computer Science (CS) educational background, but since the large mass web developers come mostly outside of this arena it is a hindrance. Seriously? A CS degree is not necessary in order to understand functional programming, and it's not like reducer functions are all that complicated.

Post by joshribakoff » Thu, Mar 01, 2018, 8:09 PM UTC

chrisco255 wrote: post #16

Future fetcher is not a replacement for Redux. It's a feature they will be adding to React later on in 2018 to allow devs to adaptively render elements based on network performance. You can signal to React to delay rendering specific components until an async operation is complete. Redux is a state management layer. Future fetching does nothing to solve app-level state management. Gross misrepresentation of Dan's tal…

Post by city41 » Thu, Mar 01, 2018, 8:23 PM UTC

awinograd wrote: post #13

The async rendering rendering stuff Dan is showing in his talk ( https://www.youtube.com/watch?v=_c7ajDXb4qw ) looks great, but I disagree that this is a redux killer. redux is useful for a lot more than just async fetching & loading. I think these new features will just reduce the scope of what redux is used heavily for.

Post by pjmlp » Thu, Mar 01, 2018, 8:41 PM UTC

joshribakoff wrote: post #37

pjmlp wrote: post #31

Earlier quoted context omitted.

I rather prefer to eventually be able to use Web Components across all major browsers.

The spec constantly evolves. At some point, there will be web components "v2" and coding "regular" web components will be outdated. As the spec evolves, browsers will evolve at different paces & implement things differently. Such is the reality of cross platform development. The only constant is change itself. To deal with it we use tools like polyfills, libs, and frameworks.