Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> That's just client side templating. Which has the same problem they all do of being greeted with a white page until ALL the content is ready.

Or being greeted with a white page period if you're using a non-JS enabled HTML client (noscript, CLI browser).



In this particular case, wouldn't they see the plain text markdown? (which in many case is just as good the html)


Kinda, it looks like they add a bit of CSS (basically make everything monospaced & pre) so the Markdown text is visible when JS is disabled (noscript), but in a CSS-less browser (e.g. links) the file is received as HTML, and the Markdown code is directly interpreted as HTML, which makes for an unreadable mess (the whole thing is a single "line" with newlines collapsed to spaces)

You're really better off using a static conversion tool, or using markdeep as a static conversion tool (with ?export)


It's 2016, if you use a non-JS enabled HTML client you better be used to the breakage.


Sure I'm used to closing the page, because really screw you if you can't display half a dozen paragraphs of text without JS.


Well, most of those websites would rather say:

Don't let the door hit you on your way out

Than spend time catering to outliers...




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: