4 ms·
The post seems rendered from markdown client-side. I fail to see how this even remotely makes sense, though.
by Wilya 14y ago
The post seems rendered from markdown client-side.
I fail to see how this even remotely makes sense, though.
- Evbn 14y agoSo its like XML+XSLT, but hipsterized?
- ihsw 14y agoNot at all, there's a certain level of sensibility in client-side rendering -- particularly because responses can contain only a skeleton structure of content, ie: JSON. Relying on a client-side language that may (or may not) be disabled, however, is simply foolish.
- anonymouz 14y agoBut roughly speaking HTML should contain the structure, and CSS the rendering information, especially if it's mostly a static page like here (maybe if you're writing a Webmail client or something it makes sense to handle more stuff on the client side). I guess the absolute horror scenario for the web would be when people start deciding to do their own personal server-side markup, and then render it with a bloated JS library on the client (hey, it's Turing complete!).
- bitsweet 14y agoWe invested a lot of time in the preview capabilities when creating a protip. We hit a small issue recently rendering the same markdown from both the client side during content creation and server side during rendering. While we fix it we just opted to temporarily do it client-side for now. It's not perfect but worked as a stop-gap measure for most.
- anonymouz 14y agoAh, I can see the reasoning there, but do not agree with it at all. Besides the inherent awfulness of this approach, my first thought was that the site is completely broken. My second one was, "Why do they want to trick me into enabling JS?".