3 ms·
I was being a smartass :) unless you are 100% you won't need multiple front-ends, doing a json api from the start simplifies things a lot. Thi
by aaronbrethorst 12y ago
I was being a smartass :)
unless you are 100% you won't need
multiple front-ends, doing a json
api from the start simplifies things
a lot.
This also presumes that I already know Backbone, Ember, React, Knockout, Batman, Angular, or whichever new JS single page app frameworks have appeared in the last 30 seconds.
Would you agree that it's easier[1] to write a web app that emits HTML than it is to write a web app that emits JSON which is consumed by a single page web app written in Javascript?
[1] Where I define "easier" in this context to mean requiring less wall clock time to get something showing up on-screen and doing something useful.
- mbell 12y agoYou don't have to use a JS MVC framework just because you built your core logic behind a JSON API. You can just as easily have a server side rendering app talk to the JSON API instead of the directly to the datastores. You get to stick with 'what you know' while still maintaining flexibility for later.
- Scarbutt 12y agoyes, but it will more complex and take up more time, which I think is what he is talking about.