3 ms·
He is getting downvoted, and rightly so, because the person is replying to has clearly set up his system is such a way that some code runs on both the server an
by tomjen3 11y ago
He is getting downvoted, and rightly so, because the person is replying to has clearly set up his system is such a way that some code runs on both the server and the client.
Which is very reasonable, btw, as it allows you to have a static site that renders for those whoes browsers doesn't run javascript and a more dynamic page for those whoes browser does run Javascript. You are guaranteed that everything renders the same way only if you excecute the same code (this can't be replaced by e.g a sensible template system because rendering might also be affected by how you, e.g, sort comments).
- bryanlarsen 11y agoWe're doing that too, but that's the boring part. That's just running client-side code on the server. It's still client-side code. You can do that in Rails too. See my other comment for more details.
- tomjen3 11y agoIf you are running client side code on the server you use a very different definition of client side code than most other people, which is bound to be confusing.