3 ms·

I think we are taking about websites that can be hosted on a static file server like Amazon S3/CloudFront, but which also have all the dynamic features of React

by kennu 10y ago

I think we are taking about websites that can be hosted on a static file server like Amazon S3/CloudFront, but which also have all the dynamic features of React available for building a rich and complex UX. For instance, when working with Phenomic (which uses Webpack), it's very easy to add any necessary React components to your project simply with npm install / yarn add. So it's really a marriage of Markdown based content publishing and interactive client-side UX.

kmonsen 10y ago
Yes, the word static is a bit overloaded here.
- gkya 10y ago
  Misused, rather. This is dynamic pages, client side.
paulddraper 10y ago
I eternally have this misunderstanding. I think static means unchanging. In this context, it means static HTTP responses, but dynamic HTML/DOM. I want a word to mean really static.
- cies 10y ago
  In this context some HTTP responses are static. The static part of the website. But the React app can also start consuming all kinds of webservice. This way (1) a large part of content can be served as prerendered static HTTP responses (HTML, CSS, JS). (2) Static content not initially loaded can be served as JSON (as seen in the presentation). And (3) dynamic content (e.g. real time comments or a chat) can be non-static (one or more webservices, possibly on WebSocket thereby going beyond HTTP). I think this may be very interesting when "big mostly static content", "need for modern web tech" and "big traffic" meet.
- bloodyowl 10y ago
  Hello, I'm in the core Phenomic team. The idea in Phenomic is that we generate for each page: - the HTML entry point, rendered like it would be with ReactDOMServer - the data-requirements of the page That lets us offer the following: - Any page is accessible directly, without runtime (which has advantages regarding performance and SEO) - Navigation works even if JS is disabled - If JavaScript is enabled, the runtime just loads the minimum required data for the next page to display and renders it Phenomic really is static, it just uses a few techniques that we learnt from the modern front-end development workflows and capabilities :)
  - paulddraper 10y ago
    Neat. Thanks for the info!

by kennu 10y ago

kmonsen 10y ago

Yes, the word static is a bit overloaded here.

gkya 10y ago
Misused, rather. This is dynamic pages, client side.

paulddraper 10y ago

I eternally have this misunderstanding. I think static means unchanging. In this context, it means static HTTP responses, but dynamic HTML/DOM. I want a word to mean really static.

cies 10y ago
In this context some HTTP responses are static. The static part of the website. But the React app can also start consuming all kinds of webservice. This way (1) a large part of content can be served as prerendered static HTTP responses (HTML, CSS, JS). (2) Static content not initially loaded can be served as JSON (as seen in the presentation). And (3) dynamic content (e.g. real time comments or a chat) can be non-static (one or more webservices, possibly on WebSocket thereby going beyond HTTP). I think this may be very interesting when "big mostly static content", "need for modern web tech" and "big traffic" meet.
bloodyowl 10y ago
Hello, I'm in the core Phenomic team. The idea in Phenomic is that we generate for each page: - the HTML entry point, rendered like it would be with ReactDOMServer - the data-requirements of the page That lets us offer the following: - Any page is accessible directly, without runtime (which has advantages regarding performance and SEO) - Navigation works even if JS is disabled - If JavaScript is enabled, the runtime just loads the minimum required data for the next page to display and renders it Phenomic really is static, it just uses a few techniques that we learnt from the modern front-end development workflows and capabilities :)
- paulddraper 10y ago
  Neat. Thanks for the info!