React+Redux VS Backbone (Marionette) in 2017?

Question

JavaScript

As a person who came from the back-end, clear MVC architectures are closer to me and Backbone is what is close to me. But! I clearly understand that with React, building the UI (building the DOM) turns into a simple and understandable scheme, where the Framework takes on most of it and does not need to be written by hand, as is the case with Backbone.View.
There are a number of questions that keep looking back at Backbone again and again. Therefore, I turn to you and I hope you put everything on the shelves for me.

1. Collections . Backbone has clear collections (a set of models) that are very convenient to work with. Search, filtering and many features from underscore, which are very useful when working with data. It is clear that React is just a View. We take Redux, but everything is exactly there there is no full-fledged functionality for working with collections. As if the collection is a simple object and process them with standard tools.
   
2. Extensibility . React in production is a "single" compiled file. Let's say I have a large application and I do not need to load the text editor when entering the main page. In cases with Backbone, I can take RequireJS to break the entire application into components and load the required component along the way, asynchronously. In the likeness of how it was done in VK. The script responsible for displaying photos is loaded only when the user clicks on the photo. As I understand it, there is no such thing in React. I hope you correct me.
   
3. Community . Because Backbone works directly with jQuery, a huge database of plugins for all occasions appears. From wysiwyg editors to modals and form validations. Accordingly, they can be loaded asynchronously using RequireJS, as described above. React is a young framework and far from all my tasks there is a ready-made solution. And this time = money to write everything by hand.
   

I understand the difference between these two Frameworks, but here are a couple of three questions stuck in my head. I hope real React adepts will come here and direct me on the right path.
Or does it still make sense to look at Backbone (Marionette) in 2017?

Answer 1

React is not a framework, but only a lib for view
1. No one forbids using lodash \ underscore to work with data. Use selectors to filter\search.
2. Use webpack to build the project, currently this is the only working solution, webpack also has asynchronous module loading - require.ensure, so you can easily break your application into chunks and load them at the right time.
3. In my opinion, there are very, very many plugins adapted for React now, for a little practice of working with this stack, I have never had the need to write something myself from 0, you can always find some solution, fork and finish it under myself.
As for the backbone, I honestly don’t know - in my opinion, React is more concise and you can quickly start writing a ready-made application on it + with the right project architecture, support in the future will be painless.

Answer 2

Look also at https://ru.vuejs.org/ and https://vuex.vuejs.org/ru/ they are somewhat similar to many of the technologies mentioned (vue.js took the best of them) and made a kind of "correct react " :)

Answer 3

In 2017, it makes sense to use either React+Redux or Vue.js. Well, certainly not Backbone, because he has not been on a horse for a long time. In any case, the choice is yours.