React Conf 2017 Livestream

You are not wrong, the talk talked about the benefits of types, but focusing on Flow

Hey, somebody actually referenced my Redux addons list! Yay! :)

Yeah, there's a great quote someone posted in a Redux issue a couple months back that summarizes things well [0]:

> Redux is a generic framework that provides a balance of just enough structure and just enough flexibility. As such, it provides a platform for developers to build customized state management for their use-cases, while being able to reuse things like the graphical debugger or middleware.

So, there's a couple ways to think about things. One is that Redux is a very simple pattern that provides just enough structure to point you in a direction, and lets you figure out what specific approaches work best for your own situation. Another is that Redux is too generic, and doesn't provide enough guidance or built-in stuff for various use cases.

I've been one of Redux's maintainers since last summer, and I've definitely seen certain requests pop up repeatedly. For example, we frequently have issues or PRs filed asking if we can modify `combineReducers` to have built-in support for iterating over and updating Immutable.js Maps and Lists. We've also had requests for `cR` to pass down the root state as a third arg to reducers by default, or something similar.

These aren't _bad_ requests, and there's clearly some valid use cases there. However, one of the key principles of Redux is that _reducer logic is just functions_. The standard answer we've given for the most part is just that "`combineReducers` is only intended for the most common and basic use case, but you should feel free to write your own reducer logic for your own use case". So, in that sense, that large list of reducer-related utilities is actually a _good_ thing, because it means people _are_ building pieces that suit their needs.

FWIW, I personally have made a major effort to add documentation and write tutorials on a lot of the more practical issues Redux users face. I wrote the FAQ [1] and "Structuring Reducers" [2] sections for the docs, and have been writing a blog series called "Practical Redux" [3] that's intended to demonstrate some intermediate to advanced concepts in the context of a sample app.

If you have any particular pain points that you feel the docs do not currently address very well, please file an issue or a PR. I'm ALWAYS happy to work with anyone who wants to improve the docs.

As for Redux vs MobX, Preethi Kasireddy's presentation today was a FANTASTIC comparison of the relative strengths, weaknesses, tradeoffs, and use cases for each of them. I highly recommend that people check it out as soon as the ReactConf recordings are posted online. Also, my React/Redux links list [4] has a section that links to several other good MobX/Redux comparisons as well [5].

[0] https://github.com/reactjs/redux/issues/775#issuecomment-257...

[1] http://redux.js.org/docs/FAQ.html

[2] http://redux.js.org/docs/recipes/StructuringReducers.html

[3] http://blog.isquaredsoftware.com/series/practical-redux

[4] https://github.com/markerikson/react-redux-links

[5] https://github.com/markerikson/react-redux-links/blob/master...

Hi. My React/Redux links list [0] has a category for Redux architecture and best practices [1], with a ton of good info.

Also, the "Redux Tutorials" category has a "Project-Based Tutorials" section [2], which points to a number of tutorials that try to build _something_ in the process of teaching. Many of those tutorials are quite a bit more complex than yet another TodoMVC example. To pick out two specific examples:

- "Building a Simple CRUD App with React + Redux" [3] is an 8-part series that demonstrates building a CRUD app, including routing, AJAX calls, and the various CRUD aspect

- My own "Practical Redux" series [4] tries to demonstrate a number of intermediate to advanced React and Redux concepts in the context of a semi-meaningful-ish sample app.

Finally, my Redux addons list has a section listing a number of interesting React+Redux apps [5], both purpose-built examples and real world projects.

Hopefully that gives you some useful examples to work with. I'd also encourage you to drop by the Reactiflux chat channels on Discord to ask questions and get feedback, at https://www.reactiflux.com . Feel free to ping me on there!

[0] https://github.com/markerikson/react-redux-links

[1] https://github.com/markerikson/react-redux-links/blob/master...

[2] https://github.com/markerikson/react-redux-links/blob/master...

[3] http://www.thegreatcodeadventure.com/building-a-simple-crud-...

[4] http://blog.isquaredsoftware.com/series/practical-redux

[5] https://github.com/markerikson/redux-ecosystem-links/blob/ma...

I think it's not that he "doesn't get to talk about tech". I think women and minorities just generally are more likely to talk about diversity because it affects them more directly and thus if you pick a diversity talk at random the speaker is more likely to fall in one of those categories -- whereas because they are the minority in tech, a tech talk picked at random will likely be by a white male speaker.

IMO it'd make sense to counterbalance this bias just like the bias for speakers in general: I'd love to hear more women and minorities talk about tech and more "straight white cis-males" talk about diversity but I'm sure someone's bound to complain if "the diversity talk" is given by a straight white cis-man because reasons[0].

I've actually noticed the "wrong narrative" you decry myself: at last year's React Conf while browsing the videos I instinctively guessed who was going to give the diversity talk by looking at the speaker. I was aware of my bias but I sadly saw it affirmed.

You don't fix the problem by talking about it. You fix it by living it. Sadly right now there don't seem to be enough high quality minority speakers to solve this without running into the "all confs sound the same" problem (more than they do already).

It's complicated.

[0]: Counterpoint: getify seems to be widely accepted as a diversity speaker but I'm not sure whether he's held talks exclusively about diversity at conferences where there weren't also women or minorities also giving diversity talks.