React and redux have achieved their prominence by holding their resolve with the Node philosophy: do one thing and do it well. React provides us with natural language and tooling for composing declarative interfaces (be they web component, native UI elements, or experiments like react-music) without seeking to blur its own lines. You've got a view. Redux establishes the same clear line: here lies the data. Either describe its changes, provoke them with middleware, or implement an alternative side effect model (redux-observable, redux-saga, and friends) but here is absolutely not the place for your view. Redux without React is still a monumentally useful library that falls under the "simple but profound" umbrella, which is also true of React sans redux. I highly doubt that Vue will manage to provide a superior model for both of these separate but foundational concerns. When one also considers that React and redux both excel in their composability and that neither library entails commitment to the other (to use React and Redux gains you two ecosystems of community support and development, neither married to the other), it seems to me that Vue will become another Angular (beloved and used wholly by very specific shops) with a few less trappings. It looks clean enough, and as a library even quite nice, but in the bigger picture it is trying to solve answered questions with poor solutions: why are we trying to replace what has been effectively & elegantly decoupled with something monolithic?