@remotesynth @stefanjudis @Igloczek @timbenniks The emergence of ISR, DPR, Edge Functions, etc are all beyond pre-generated assets, and yet they fit perfectly into a composable architecture model where no server is part of the infra or mental model of serving sites and apps... things at the heart of a Jamstack mindset.
...
@remotesynth @stefanjudis @Igloczek @timbenniks The update to the definition removes explicit mention of pre-generation (although I consider that very desirable to this day) because otherwise it is interpreted as ONLY pre-generated assets.
...
...
@remotesynth @stefanjudis @Igloczek @timbenniks I'd agree with @stefanjudis, in that it was never really a stack. More of an approach. (see "naming is hard")
That fact made it hard to really define in a way that ages well as new technologies and practices arrive.
...
That fact made it hard to really define in a way that ages well as new technologies and practices arrive.
...
@remotesynth @stefanjudis @Igloczek @timbenniks Ah!
Naming is hard.
As is keeping things clear per the history and memory of the web, it seems!
That page should have gone leaving one definition.
Earlier in the year some work was done to try to help keep the term current, while also attempting not to just wildly pivot...
Naming is hard.
As is keeping things clear per the history and memory of the web, it seems!
That page should have gone leaving one definition.
Earlier in the year some work was done to try to help keep the term current, while also attempting not to just wildly pivot...
@jakelear My cooking repertoire is about to sky-rocket.
Phil Hawksworth
@philhawksworth •
Now do every other recipe https://twitter.com/deoncole/status/1574126193607004160
@jlengstorf @cassiecodes This phrase is an absolute bullseye!
@timbenniks Yeah I like that.
It's how I think of a build server.
The fact that modern web hosting can abstract that layer away and do clever caching things behind the scenes without you needing to include any of that in your mental model is reason to celebrate.
Whatever we call it.
It's how I think of a build server.
The fact that modern web hosting can abstract that layer away and do clever caching things behind the scenes without you needing to include any of that in your mental model is reason to celebrate.
Whatever we call it.
@zachleat @bram_stein yyyyes!
@timbenniks Yeah. The key is in how things get to the CDN. What do you have to understand? What is the flow and what infra is involved in serving your site (vs generating it).
I like servers that can go away.
I waxed lyrical on this topic in 2018 in this post
https://www.hawksworx.com/blog/webserverless/
I like servers that can go away.
I waxed lyrical on this topic in 2018 in this post
https://www.hawksworx.com/blog/webserverless/
@timbenniks I’d argue that just having a cache layer falls short of it being Jamstack.
But if you can totally decouple the server that generated the views from the requests that come from the users, then maybe the term holds.
It’s that decoupling which is core to Jamstack
But if you can totally decouple the server that generated the views from the requests that come from the users, then maybe the term holds.
It’s that decoupling which is core to Jamstack
@AlexanderTrefz @johnallsopp @ffconf It wasn’t. I was calling how browsers handle HTML fault tolerant. The Robustness Principle is a cornerstone of the web. HTML and browsers were designed specifically with this in mind and the web could never have become widespread without it.
@AlexanderTrefz @johnallsopp @ffconf I respectfully disagree. The web could never have established a foothold or feasibility as a global, decentralised, democratic platform without HTML and the robust fault-tolerant support of it in web browsers.
It’s a beautiful thing.
It’s a beautiful thing.
@ascorbic @EmmettNaughton @zachleat @chriscoyier @hankchizljaw @Netlify ✨Feature request issue created ✨
@ascorbic @EmmettNaughton @zachleat @chriscoyier @hankchizljaw @Netlify Yeah, I only discovered this during this update. I think it would be a very helpful addition to the Netlify geo object.
@SamKap I'm cheered and booed in equal measures across the various Netlify internal teams for this nonsense.
@ascorbic @EmmettNaughton @zachleat @chriscoyier @hankchizljaw @Netlify Not for timezone localisation.
I use that to label the city and country the time is localised to, but getting the time in a specific timezone in JavaScript needs you to specify the timezone in the IANA timezone db format which has complex mappings
https://en.wikipedia.org/wiki/Tz_database
I use that to label the city and country the time is localised to, but getting the time in a specific timezone in JavaScript needs you to specify the timezone in the IANA timezone db format which has complex mappings
https://en.wikipedia.org/wiki/Tz_database
@ChrisFerdinandi @zachleat @chriscoyier @hankchizljaw @Netlify Thanks Chris!
The site lives on.
Its implementation is less comical demo fodder.
The site lives on.
Its implementation is less comical demo fodder.
@EmmettNaughton @zachleat @chriscoyier @hankchizljaw @Netlify Hoping that got it!
I'm doing some very basic IPv4 lookup for the locale, so I needed a fallback.
I'm doing some very basic IPv4 lookup for the locale, so I needed a fallback.