4 ms·

What I wonder is why static, I come from blogging with dos blog( untile godaddy broke it). And while I never understood the use of plugins like silverlight or

What I wonder is why static, I come from blogging with dos blog( untile godaddy broke it). And while I never understood the use of plugins like silverlight or adobe I don't really see the harm in using a native js framework to pull the artical contents from the server and update the DOM over pulling and retemplatizing the whole html page. Am I missing something or is static more of a mind set gained from dealing with sites that need to draw the first render faster and handle larger scale in a day then my little old blog will see in a life time?

pier25 6y ago
The point of using a SSG and deploying to a static host is that hosting becomes extremely simple. No need for a database, HTTPS included, deploying is just copying files, CDN is already included, and it's either free or very cheap. If you're ok with editing code files (markdown, html, etc) this is extremely simple to setup. You can even get a template somewhere[1] and just start producing content. Obviously this is only feasible for devs or maybe designers with HTML/CSS skills. I'd like to add that SSGs can also render dynamic data from an API or directly from a DB at build time. [1] https://jekyllthemes.io/ https://jekyllthemes.io/
cercatrova 6y ago
That site is still static. Static doesn't mean there's no dynamic content but rather that no new files are sent from the server, including new JS files. If you ship the entire JS framework on page load, then the page is still static.
- pier25 6y ago
  You can have a static SPA with code splitting though.
  - cercatrova 6y ago
    Yeah I agree, what do you mean by "though"?
    - pier25 6y ago
      Well, you said: > no new files are sent from the server But you can have 'static' with code splitting and send new files from the server on each route change.
      - cercatrova 6y ago
        Well it's more like, if there's a file bundle, it can be served, but no new files will be generated by the server and sent. The code split files already exist on the server, they're not generated anew so yeah it's still static.

pier25 6y ago

The point of using a SSG and deploying to a static host is that hosting becomes extremely simple. No need for a database, HTTPS included, deploying is just copying files, CDN is already included, and it's either free or very cheap. If you're ok with editing code files (markdown, html, etc) this is extremely simple to setup. You can even get a template somewhere[1] and just start producing content. Obviously this is only feasible for devs or maybe designers with HTML/CSS skills. I'd like to add that SSGs can also render dynamic data from an API or directly from a DB at build time. [1] https://jekyllthemes.io/ https://jekyllthemes.io/

cercatrova 6y ago

That site is still static. Static doesn't mean there's no dynamic content but rather that no new files are sent from the server, including new JS files. If you ship the entire JS framework on page load, then the page is still static.

pier25 6y ago
You can have a static SPA with code splitting though.
- cercatrova 6y ago
  Yeah I agree, what do you mean by "though"?
  - pier25 6y ago
    Well, you said: > no new files are sent from the server But you can have 'static' with code splitting and send new files from the server on each route change.
    - cercatrova 6y ago
      Well it's more like, if there's a file bundle, it can be served, but no new files will be generated by the server and sent. The code split files already exist on the server, they're not generated anew so yeah it's still static.