I wrote about Remixing REST APIs with GraphQL [1], and more in-depth discussion of application-level consistency (or correctness) when using GraphQL queries and mutations [2].
When it comes to UI need to start thinking past Framework A vs Framework B.
There is already a browser-native compatibility layer known as the Web Components API that allow components rendered by different frameworks to work together, so we won't ever have to be stuck in Framework A or Framework B and can migrate in agile manner (one component at a time) from one to the other or whatever new framework may come next year. I agree Web Components have some major warts and DX issues but libraries like SkateJS and others help smooth those out.
Copying from Readme my WIP project that uses Skate:
"SkateJS allows us to export components rendered by React, Angular 2, 4, Vue, and other modern composition-oriented frameworks as W3C Custom Elements and compose those Custom Elements into higher order Custom Elements with data flowing from parent to descendants and so on.
With SkateJS we can have an Angular 4-rendered Form custom element composing Angular 2-rendered input and selection custom elements, or the other way around with Angular 2-rendered Form custom element composing Angular 5 --and Angular 4-- rendered input and selection custom elements.
SkateJS also provides a Router that is framework agnostic. Only the rendering part of any framework (Angular, React, Preact, Vue, et al) is ever used.
This way we can build SkateJS-based reusable component libraries using any version of Angular (> 2), React, Vue et al and be able to use those components in our SkateJs-based site together, including via composition, and be able to upgrade our app (when a new version of React, Angular or Vue et al comes out) one component at a time, in piecemeal fashion as in iterative agile development, as opposed to having to do it all at once, as in waterfall development, which is almost always an unrealistic approach. This works because our components are essentially all custom elements regardless of rendering library we use (different versions of Angular, React, Preact, Vue, et al)"
I think he might have also meant free access to "money" itself as in basic income. Potentially, in an enlightened society that we will never have, you could apply for additional basic income to cover more than your basic needs, stuff like education, books, free access to paid research papers, etc. That is probably what he meant by free access, not that people wouldn't be rewarded for their hard work. Just less BS.
Vue.JS could have a better shot at being respected if it drops the mixing of declarative and imperative code (logic in HTML) as that introduces a dichotomy in its world view that is hard to eliminate.
I wrote this post on "P2P Energy Economy" [1] back in 2009 when Bitcoin was new and Satoshi mentioned in his one and only email [2] to the P2P Foundation list that it could be based on Bitcoin, but I could not align the ideology of Bitcoin with the ideology I started with, which is that money should be useful in and of itself. Now I can see what he meant.
[1] https://github.com/idibidiart/the-great-api-masher [2] https://github.com/idibidiart/the-great-api-masher#maintaini...