4 ms·
I dislike having to write a separate front-end and back-end and worry about APIs and JWTs and security and Redux and multiple servers coupled with isomorphic Re
by freehunter 6y ago
I dislike having to write a separate front-end and back-end and worry about APIs and JWTs and security and Redux and multiple servers coupled with isomorphic React being more pain than it's worth when I could just as easily not use React.
I'd use React on every project if I could run it like a Rails front-end instead of needing to write distinct server and client side applications.
- terandle 6y agoHave you looked at next.js? It allows you to write your server side database access code/etc in the same place as your react client side app. Pretty neat, however I personally would rather write my backend code in something better than JS so I don't go that route.
- memexy 6y agoNot sure I follow. Reactive frameworks includes more than React. Reactive frameworks generally mean some form of observables, observers, and mechanisms for linking the two together via a dataflow graph, e.g. http://reactivex.io/documentation/observable.html http://reactivex.io/documentation/observable.html. > This page explains what the reactive pattern is and what Observables and observers are (and how observers subscribe to Observables). Other pages show how you use the variety of Observable operators to link Observables together and change their behaviors. I'm not familiar with React so I'm not sure how all these concepts are implemented in React.
- c17r 6y agoLook into InertiaJS. Svelte/Vue/React become just the UI piece and everything else (routing, validation, etc) is handled server side