4 ms·

I'm not sure if this counts as a "static website", since the page is not delivered exactly as stored. It requires JavaScript to actually renders the page, which

by bbx 10y ago

I'm not sure if this counts as a "static website", since the page is not delivered exactly as stored. It requires JavaScript to actually renders the page, which seems like an overkill.

Already__Taken 10y ago
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. If someone is prepared to accept this it's not that hard to accept generating the html page yourself and uploading that.
- masklinn 10y ago
  > 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).
  - coldtea 10y ago
    It's 2016, if you use a non-JS enabled HTML client you better be used to the breakage.
    - masklinn 10y ago
      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.
      - coldtea 10y ago
        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...
  - laurent123456 10y ago
    In this particular case, wouldn't they see the plain text markdown? (which in many case is just as good the html)
    - masklinn 10y ago
      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)
raimue 10y ago
I fully agree. Why render it in every client when you can do it only once on the server? This feels like a waste of CPU resources.
- accordionclown 10y ago
  compared to all the other things your cpu is doing, and all the time your cpu sits there doing nothing, the "waste" in this case pales to total unimportance. you've got a supercomputer; you might as well use it.
  - raimue 10y ago
    An idle core will definitely use less power than one constantly processing. That is what drains the battery in your laptop. I'd rather not spend my battery power if it can be done on the server instead.

by bbx 10y ago

I'm not sure if this counts as a "static website", since the page is not delivered exactly as stored. It requires JavaScript to actually renders the page, which seems like an overkill.

Already__Taken 10y ago

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. If someone is prepared to accept this it's not that hard to accept generating the html page yourself and uploading that.

masklinn 10y ago
> 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).
- coldtea 10y ago
  It's 2016, if you use a non-JS enabled HTML client you better be used to the breakage.
  - masklinn 10y ago
    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.
    - coldtea 10y ago
      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...
- laurent123456 10y ago
  In this particular case, wouldn't they see the plain text markdown? (which in many case is just as good the html)
  - masklinn 10y ago
    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)

raimue 10y ago

I fully agree. Why render it in every client when you can do it only once on the server? This feels like a waste of CPU resources.

accordionclown 10y ago
compared to all the other things your cpu is doing, and all the time your cpu sits there doing nothing, the "waste" in this case pales to total unimportance. you've got a supercomputer; you might as well use it.
- raimue 10y ago
  An idle core will definitely use less power than one constantly processing. That is what drains the battery in your laptop. I'd rather not spend my battery power if it can be done on the server instead.