The ecosystem around React is huge. But you don't have to use anything to build an application with React. [0] For instance, most people try too early to use a state management library. But you don't have to use it from the start [1], because React comes with its own internal state management. It makes sense to learn the React fundamentals first and build your own application with it [2] before you dive deeper into the ecosystem [3].
- [0] https://www.robinwieruch.de/reasons-why-i-moved-from-angular...
- [1] https://medium.com/@dan_abramov/you-might-not-need-redux-be4...
Reasons: - I already know Rails so there is no learning curve
- It takes care (alone or with gems) of security, user management, routing ... with very few configuration details
- I can still deploy it quickly on one single droplet with capistrano
Recently I started to learn Vue.js and I think - for me - they will make a great combination for the web apps that I need.
I have worked in Django (6 months) as well but not as much as I have worked in rails (3 years)
Thanks
I definitely recommend it, I am really enjoying his teaching style and the course is structured very well.
For others, it could be rails, phoenix, flask etc. In case of a shippable product, time to market is very important, both to validate your product and boost your own morale and confidence.
I also quite like Django, but I am tempted to pick up Flask at some point and use it in anger, as I've only toyed with it in the past.
Django has cool libraries like django-rest-framework but, after reading the source, I just get a better feeling from Flask.
I haven't hit many bugs in either, so from an in-practice perspective both should be fine.