Add rdx as an alternative. #489
Conversation
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Thanks for PR. It seems that this project is neither popular, nor being actively worked on, nor up to date (e.g. uses Babel 5). For these reasons I will close this PR, but feel free to resubmit if it gains some traction or if you actively invest time and effort in it. |
|
@gaearon The point of the pull request was to gain traction. Also, Babel 5 is intentional. |
|
Babel 5 is not supported anymore. It doesn't get any bugfixes and implements outdated specs. We can't recommend a tool relying on it to the users, even if that was intentional, because when they have a problem, they'll blame React ecosystem for this. |
|
Ok but in order to have users I need to tell people about it and why update |
|
It is, and partly because the market for these tools is oversaturated by now. Just adding your tool to the list won't help you gain meaningful usage because people won't see why choose your tool over more popular other tools with more active development and recent dependencies. In the end, to beat them, you would need to create something that is so much more compelling than alternatives that people get excited about it and spread the word. It also means writing blog posts, making tutorials, sending pull requests to popular open source project examples to use your tool, talking to the users on social media platforms to learn what they want, preparing promotional materials (like tweets), reaching out to influencers, etc. Open source is a lot of work, and having a project is not enough. Building a community starts with talking to people, not just making a project and asking others to link to it, although this is definitely a good first step. I would make an exception if I was captivated by the README in some way and thought other people would be too, but at this point I'm not convinced yet. Sorry, and I hope this helps! |
|
Also, I don't mean to discourage you. I know it's hard to promote a project if nobody knows you unless you hit the sweet spot of virality. Learning this takes a lot of time and practice. I would recommend contributing to existing tools with similar focus first, and getting to know the people behind them, as well as their users and problems. This will give you a deeper insight into how to market your tool, how to position it differently from the rest, and how to convince some percentage of the users that it is the right choice for them. Helping maintain similar tools and sending pull requests is a good way to get immersed in that community. |
|
I wrote a fairly long comment on HN a while back on the topic of marketing a Redux-related library: https://news.ycombinator.com/item?id=11833301 . A good chunk of the comment is specific to that lib, but much of the info applies here as well. |
|
@gaearon Thank you for taking time to share your advice with me, I appreciate it :) |
|
@gaearon RDX is now at v2.0.0 and uses Babel 6 as well as some other clean-up and fixes. WebPack 2 is planned but there is research to be done for that first. Can I get you to accept it to the list now!? :) |
|
@gaearon Would I have to make a new PR for that or can this one be reopened? |
|
If it gets meaningful usage then yes, I'd be happy to take another look. |
|
Ok, that seems fair, thanks for getting back :) |
No description provided.