Hey @ElJefeVador The reason why I personally prefer react over any other framework is exactly for that reason - it only comes bundled with the minimal amount of things you need. This keeps react very lightweight and focused on purely displaying information based on the state of the application. To me, this allows for as pure JS code as possible while still using a framework to hook into things like event loops. To cover the routing, that is also partly where react is very nice. Instead of react having a specific idea of how you should do routing, they let you determine it yourself. That doesn't mean react doesnt have a preferred routing system though, there is React-Router (https://reactrouter.com/) which is maintained by nearly the same react dev team. They just keep it as a separate project so you can choose which things ya need and have no extra fluff. This is really good because sometimes you can create react apps without even needing the router, such as a simple single page app.
Heya @SrMouraSilva Im gonna be doing the base setup for the new react system for i5 and I love your questions. In regards to open sourcing it, I don't think thats a possibility at this time. The restructure to react is going to take a bit for the core staff to get used to and I want to make sure that the correct setup is done before that could ever happen. Without getting into too many specifics, there just needs to be a flow that everyone gets used to which will make participation easier for any dev to work with. If you want to participate please contact unleashed regarding that! The front end will be react and the backend will be graphql. The middle layer will be apollo-graphql. I am hoping to use a lot of the new things that React Storybook has provided for testing and CI, which can mock backend requests through apollo-graphql. This will take at least a few weeks to set up, and also my intention is to teach as many people as I can what I know, so to have a stable build that we can get started with will take a little bit.