3 ms·
The promise of front end frameworks is realized by startups when using a BaaS (backend as a service) - like Firebase. The idea is that you only have to worry a
by dfee 8y ago
The promise of front end frameworks is realized by startups when using a BaaS (backend as a service) - like Firebase.
The idea is that you only have to worry about one environment (the browser - yeah, I get the irony) and one deployment instead of multiple (the former plus backend deployment, monitoring, etc.).
The second you start worrying about SSR (server side rendering) you’re suddenly taking on the complexity of writing a backend again.
- dvasdekis 8y agoMy understanding of node's birth and rapid rise was that it was "backend tooling for frontend-devs" - suddenly it gave the front-end teams the power they needed to launch quickly using what they knew. I've been looking for quite some time for "front-end tooling for back-end devs" without success - there are some great frameworks like Postgrest or Hasura which take you from Database through to API interface, but then you're faced with raw Javascript and all that pain synchronising browser state with the API via a web-worker. My attempts to use Vue & React have just resulted in the exchange of one kind of complexity (raw Javascript state change) with another (learning the framework). I'm all ears, if anyone has used anything (framework, IDE, WYSIWYG editor, some SAAS app, anything) that simplifies the journey from OpenAPI spec to a webpage with a UI that changes as the API returns things.
- ppeetteerr 8y agoThere are many tools that will turn backend code into interactive UI, but they generate a mess on the front-end.