3 ms·
What about graceful degradation? Making JavaScript a requirement instead of an addition is plain wrong and goes against the essence of the Web.
by regularjack 15y ago
What about graceful degradation? Making JavaScript a requirement instead of an addition is plain wrong and goes against the essence of the Web.
- rimantas 15y agoOnly if "Web" for you consist of mostly static content. For others there is an interesting thing called Web Applications. How do you gracefully degrade a game done with all cool stuff HTML5 and friends offer?
- regularjack 15y agoNo, I'm not talking about static content, I am talking about dynamic content, which is exactly what Rails is there for. If you only have static content you don't even need Rails, just have the web server deliver it. I was not talking about "Web Applications" either, which, FYI, are not the same thing as dynamic content. I realize that he mentions in the post that he's mostly talking about Web Applications, but then he's just stating the obvious and the post title should be "For Web Applications, Rails is just an API".
- virtualeyes 15y agoRails is there to generate static content as the alternative, hitting the Rails stack for live data, is asking for trouble -- just ask Twitter ;-) Of course by saying such a thing on a Rails thread, I am clearly asking to accrue yet more karma. I can take it, the truth hurts, I'm a compile time Boddhisatva brought here to enlighten the heathens, willing to descend into runtime hell to save all beings and bring them to the other shore of static compilation. May all beings be snappy (and never sluggish)