Hey. I think I'm in a pretty good position to give you some feedback. As background, I maintain a well-received list of high-quality React and Redux tutorials and articles [0], and a catalog of Redux-related libraries, addons, and utilities [1]. I also spend a lot of time hanging out in the Reactiflux chat channels, and apparently currently have the messages posted in Reactiflux since the service moved to Discord [2]. Finally, I wrote the official Redux FAQ page from scratch [3]. So, while I'm not a public name in the React community like Dan Abramov, I'm pretty in tune with what's going on in the ecosystem.
The first thing to consider is that the size of the target market for any "addon", "mod", or "extension" for any technology is, by definition, limited to the size of the user base for the original technology. While Redux is certainly popular, and basically the winner of the "Flux Wars", you're limited to a subset of the JS dev community.
A second factor is idiomatic usage. Any framework ecosystem is going to have an idiomatic way of doing things. Tutorials will teach those same idioms, training classes will teach those idioms, people will write apps using those idioms, and the vast majority of the userbase is going to share those idioms. When you start going outside those idioms, fewer people will understand your approach, and fewer people will be interested in something that's not "the normal way".
Redux is fairly minimal, so similar to Backbone, there _is_ a fairly active ecosystem with people adding numerous different spins in usage, and additional layers on top, like yours. However, only a few of those have gained particular traction (like redux-saga). Idiomatic Redux tends towards explicit and functional, rather than implicit and object-oriented.
Third, there are a number of overlapping approaches and implementations being developed by different people, as you can see by browsing my addons catalog. Two dozen libraries implementing "local/component state" in various ways, a dozen more for "subscribe to changes in a slice of state", and I don't know HOW many approaches to handling "side effects". Not sure how much of that is people not knowing what else is out there, how much is "Not Invented Here" syndrome, and how much is people just trying to scratch an itch. So, any one addon in a given category is somewhat competing for mindshare, and only a few will really get attention.
Fourth, honestly, a lot of it really is actually getting the attention of the "thought leaders and influencers". I signed up for Twitter just so I could actually reply to some of the conversations I saw going on, and when Dan saw that, he tweeted out that I'd just joined. Five minutes later I had 30 followers, and 100 by the end of the day. Small potates as Twitter goes, obviously, but the point is that people followed me just because Dan said I was interesting. (I'm not, really :) ) The "Doing Whatever Dan Abramov Tells Me To Do" fake book cover has a bit of truth to it [4]. Now, I'm not saying go harass Dan, or Ryan Florence, or Christopher Chedeau, but when core members of the React/Redux community point at stuff, other people look. And, that said, Dan does tweet out anything that looks vaguely interesting, so tweeting him a link is a valid approach.
So, Radical. I _do_ actually have Radical listed in my addons catalog, but I have it listed on the "Variations" page [5], which is where I list libraries that are distinctly deviating from the idiomatic Redux approach (and, as you'll note, there's quite a few of those). Looking at it, there's good points and bad points.
Good:
- "Reducing boilerplate" is certainly a viable selling point. One of Redux's core principles is that things are explicit rather than implicit, but obviously many people dislike much of the verbosity. So, that's a good focus.
- Radical has documentation. Like, _real_ documentation. An actual description that tries to give a motivation and explanation, some meaningful code samples, and API docs. The average JS lib on Github has a short repo one-liner, maybe a couple paragraphs in the README, and a five-line code snippet with very little explanation for where it fits in. This is decidedly a good thing.
Mixed:
- Focus on grouping actions and reducers. Again, there's numerous opinions and ideas, and putting those together _is_ one semi-popular approach (per the "Ducks" concept), so it's not unheard of. On the other hand, Dan encourages arbitrary reducers responding to arbitrary actions to prevent coupling, and that's considered the idiomatic approach.
- Use of Typescript in the lib and the samples. There are certainly Typescript users in the Redux community, but ES6 is the common approach.
Bad:
- Use of an OOP approach to managing things. I know it's still dispatching actions and such and updating its own slice of the store, but the Redux community is heavily influenced by Functional Programming, and as such an OOP approach is less likely to gain interest.
- The fact that you do need to hook the generated reducer into the store isn't as clearly called out as I'd like to see.
- Lack of a full-blown example written using Radical. Again, the fact that you have actual code samples is good, but if this is such a big improvement, a "real" app example would go a long way to show that.
- Both the docs and the source are in single files. Both might be easier to read through if they were split into smaller pieces.
- There's a number of libraries that look like they do something fairly similar. The list at [6] has many that are more component-oriented, but there's some overlap. The list at [5] also has some similar options.
Overall, it looks like a well-written library, with a valid use case, but the fact that it's a non-idiomatic approach means there won't be as much interest, and therefore fewer users _and_ fewer people willing to pass it along.
For what it's worth, I hang out in the Reactiflux chat channels [7] evenings EST if you'd like to drop in and talk about it.
[0] https://github.com/markerikson/react-redux-links
[1] https://github.com/markerikson/redux-ecosystem-links
[2] http://pipend.github.io/reactiflux-dashboard/#/fame?ago=1+ye...
[3] http://redux.js.org/docs/FAQ.html
[4] https://twitter.com/ThePracticalDev/status/71846227233570406...
[5] https://github.com/markerikson/redux-ecosystem-links/blob/ma...
[6] https://github.com/markerikson/redux-ecosystem-links/blob/ma...
[7] https://www.reactiflux.com