Comment by acemarke | Hacker News Reader

Comment by acemarke | Hacker News Reader

Parent Full thread

Yes, Redux by itself knows nothing about React. But, the vast majority of Redux users are using React, and it's a reasonable shorthand to just say "Redux" in this case. It's also how most end users would tend to refer to things.

FYI, I'm a Redux maintainer. We are currently working on an internal refactoring of React-Redux's `connect` so that it will use the new `React.createContext` API instead of legacy context. We've got two open PRs with "competing" reimplementations, and I will actually be spending the rest of today hacking on those.

The immediate goal is to make React-Redux at least compatible with React's upcoming "async rendering" capabilities. However, we do have some difficult problems to solve in order for Redux to take full advantage of the "Suspense" feature. We've got a decent idea what the problem space is, but we need some more examples and guidance from the React team so we can try to work on a solution.

Side note: we're also hoping to completely rework the React-Redux docs (since they're mostly just a jargonistic API reference in a Markdown file in the repo), and we're also considering a restructuring / reworking of the core Redux docs as well. Would love to have some suggestions or even additional volunteers to help us!

Issues/links for reference:

- Roadmap: https://github.com/reduxjs/react-redux/issues/950

- v6 WIP PRs: https://github.com/reduxjs/react-redux/pull/995 , https://github.com/reduxjs/react-redux/pull/1000

- React-Redux docs: https://github.com/reduxjs/react-redux/issues/1001

- Redux core docs: https://github.com/reduxjs/redux/issues/2590

The egghead Redux series has been very popular and useful for users. We’d love to talk about how we can compliment this documentation revamping with updated/new free resources. joel@egghead.io

Yep, it's highlighted in our README and "Learning Resources" docs pages, and it's the first thing I recommend after the docs in my own "Suggested Resources for Learning Redux" blog post ( http://blog.isquaredsoftware.com/2017/12/blogged-answers-lea... ).

Leave a comment in issue 2590, or DM me on Twitter or something - happy for any assistance you can offer!

I live in an Angular world, and a lot of what you’re describing sounds like ideas that are common in many Angular setups, with async rendering of state not completing until a data stream holding state passes through an async pipe in the template/view.

How much conversation is there with the ngrx (AngularRedux implementation with Redux as a leaf-able RxJS stream) folks? This is essentially an async integration, wondering if there is some good additional idea exchange to be had there.

I haven't used RxJS or Angular myself, but my impression is that the React "Suspense" capabilities are pretty novel compared to other JS frameworks. Check out Shawn Wang's "fresh-async-react" repo for a list of resources explaining the concepts: https://github.com/sw-yx/fresh-async-react .

Honestly, the NgRX team is completely separate and we don't talk. I proposed a get-together back in March when I was out in SF for a few days, but it didn't pan out (see the thread before and after this tweet: https://twitter.com/acemarke/status/969035239392776193 ). I'd love to have some discussions to see where we can maybe share some ideas, see where the ecosystems actually overlap, etc.

The ReactReason devs seem to be averse to adding the context API (fears of instability). Does the Redux team have any similar reservations?

I haven't looked at ReactReason beyond seeing it mentioned in a few conference slides.

The new context API (`React.createContext`) is intended to be stable going forward. As far as I know, the only potential "unstable" aspect remaining is the `changedBits` prop for potentially optimizing which consumers actually update on a given context value change. So no, I don't have any particular reservations at the moment. Legacy context still works but is very deprecated, and new context allows us to refactor the internals in a way that's ultimately simpler and hopefully more compatible with where React is going.

Can you point me to some of these ReactReason discussions?

https://github.com/reasonml/reason-react/issues/199#issuecom...

It's one of the big reasons our company isn't even considering ReactReason at present. Lack of support for version 16 APIs is killer when you already have stuff depending on them.

Huh. I'm very surprised to see that comment coming from Cheng Lou. React 16.3 came out in March, and the React team has been encouraging everyone to use the new context API since then. Really not sure what's behind his comment.

Reply on news.ycombinator.com