2 ms·
When MVC front-end frameworks were taking off (back in the Ember.js days) I imagined a future where you'd have a combined backend + frontend framework and you c
by Nextgrid 6y ago
When MVC front-end frameworks were taking off (back in the Ember.js days) I imagined a future where you'd have a combined backend + frontend framework and you could interact with data objects from the frontend directly like you'd use an ORM on the backend and all the communication, synchronization, data serialization, etc abstracted away (obviously with security restrictions enforced on the backend).
Meteor.js was the only serious attempt at this but it was too different from the status-quo (for most projects, SQL is what you want - MongoDB will bring lots of problems down the line) and never caught on.
Instead, 10 years later, we still mostly have a mess of everyone reinventing the wheel and doing most of the API communication, de/serialization, error handling manually. MVC has never taken off on the frontend either despite it being a good fit for most projects in my opinion. We have things like GraphQL, websockets, etc and yet still nothing that takes all of those together and provides a no-BS development experience comparable to backend frameworks like Django, Rails or Laravel.