3 ms·
That's all well and good, if you do your API with Rails. Assuming this is an actual API, consider a rouge script slamming your API, whoops, your main app is ou
by rubynerd 15y ago
That's all well and good, if you do your API with Rails.
Assuming this is an actual API, consider a rouge script slamming your API, whoops, your main app is out as well, nobody is signing up for your service.
Assuming this is for backbone/batman/other-generic-clientside-framework, nope. Too much JavaScript makes everything seem sluggish, and I really don't want to reimplement everything twice (once in Rails for conventional browsers and for people who disable JavaScript, second in client-side MVC)
- techiferous 15y ago> for people who disable JavaScript I stopped caring about this long ago. I write database-backed web applications that require authentication, and in this context if a user has JavaScript turned off, that's their problem, not mine.
- pdwetz 15y agoSort of funny; as soon as I hit a new site that requires javascript, I often run away! But of course that's my problem; I get why user preference would get in the way of your clean implementation. :)
- coderdude 15y agoWell, when you cripple your own client there's not much you can ask for.