4 ms·

Here is what is missing now in the React ecosystem http://guides.rubyonrails.org/ http://guides.rubyonrails.org/ Thats it. A central place with an organised l

by spion 10y ago

Here is what is missing now in the React ecosystem http://guides.rubyonrails.org/ http://guides.rubyonrails.org/ Thats it. A central place with an organised list of guides. Not a blog though. Also must cover things such as redux, mobx and routers, and how it all fits together.

acemarke 10y ago
I already have something pretty close to that :) I keep a big list of links to high-quality tutorials and articles on React, Redux, and related topics, at https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links . Specifically intended to be a great starting point for anyone trying to learn the ecosystem, as well as a solid source of good info on more advanced topics. (The entire list has just been me working it by myself with the occasional "add a link" PR from random other people, but I'd certainly appreciate any actual offers to help improve it, especially since my own knowledge is rather limited in a number of areas.)
- lucaspiller 10y ago
  The work you have done here is useful, but as pointed out in the original article, articles very quickly become outdated in the Javascript ecosystem. It's not just how libraries work (I haven't looked through the list too much, but I'm sure there are plenty of articles suggesting a Webpack 1.x configuration) but also the recommended way of doing things and what tools to use that changes. I guess this is one of the advantages Rails has being a monolith - as it provides nearly everything, it's very easy for them to keep up to date documentation of the 'Rails way' to do things. React and Redux have been relatively stable, but it's everything else that goes along with it that is the issue.
  - acemarke 10y ago
    True, but it's also worth noting that the existence of a newer version of a lib doesn't completely invalidate the older version. For example, Webpack 2 _is_ out, but a Webpack 1 config and setup will still keep working just fine. Ditto for, say, React-Router v3 vs v4.

by spion 10y ago

acemarke 10y ago

I already have something pretty close to that :) I keep a big list of links to high-quality tutorials and articles on React, Redux, and related topics, at https://github.com/markerikson/react-redux-links https://github.com/markerikson/react-redux-links . Specifically intended to be a great starting point for anyone trying to learn the ecosystem, as well as a solid source of good info on more advanced topics. (The entire list has just been me working it by myself with the occasional "add a link" PR from random other people, but I'd certainly appreciate any actual offers to help improve it, especially since my own knowledge is rather limited in a number of areas.)

lucaspiller 10y ago
The work you have done here is useful, but as pointed out in the original article, articles very quickly become outdated in the Javascript ecosystem. It's not just how libraries work (I haven't looked through the list too much, but I'm sure there are plenty of articles suggesting a Webpack 1.x configuration) but also the recommended way of doing things and what tools to use that changes. I guess this is one of the advantages Rails has being a monolith - as it provides nearly everything, it's very easy for them to keep up to date documentation of the 'Rails way' to do things. React and Redux have been relatively stable, but it's everything else that goes along with it that is the issue.
- acemarke 10y ago
  True, but it's also worth noting that the existence of a newer version of a lib doesn't completely invalidate the older version. For example, Webpack 2 _is_ out, but a Webpack 1 config and setup will still keep working just fine. Ditto for, say, React-Router v3 vs v4.