@kentcdodds @mrkurt @Netlify @vercel @flydotio The UI team's concerns are decoupled from the infra team's and they work in Jamstackland (which is a theme park we may or may not one day open)
While the teams working on the APIs are in more traditional stacks and deal with very different challenges.
While the teams working on the APIs are in more traditional stacks and deal with very different challenges.
@kentcdodds @mrkurt @Netlify @vercel @flydotio I think that's fair.
But we should probably not forget that APIs are a big enabling part of Jamstack. And those APIs might be build with anything! The decoupling is key.
https://app.netlify.com is a Jamstack app.
- Pre-generated React UI
- All sorts of services via APIs
But we should probably not forget that APIs are a big enabling part of Jamstack. And those APIs might be build with anything! The decoupling is key.
https://app.netlify.com is a Jamstack app.
- Pre-generated React UI
- All sorts of services via APIs
@kentcdodds @Netlify @vercel An Express server typically is a long-lived process which might internally manage state etc, rather than an execute-and-terminate process, so I'd say so, yes.
(Which is not to say somebody might use Express in a serverless function) to return a view and do nothing more.
(Which is not to say somebody might use Express in a serverless function) to return a view and do nothing more.
@kentcdodds @Netlify @vercel And if anyone replies to inform me that "there is always a server", I might have to climb directly into the sea.
:)
:)
@kentcdodds @Netlify @vercel ...so for me, the question of SSR is less about "is on-demand?" and more about "is there a server in my problem space?"
@kentcdodds @Netlify @vercel ...serverless functions are perfect "companions" to pure Jamstack, which have blurred the edges and extended the paradigm.
They can provide on-demand generation of views without introducing servers or the friction that serverful development workflows bring...
They can provide on-demand generation of views without introducing servers or the friction that serverful development workflows bring...
@kentcdodds @Netlify @vercel I might once have been a strict purist and said, "Nope. With Jamstack you pre-generate all the assets. And use progressive enhancement to do things in the browser"
And where the project suits, that is always my preference.
But...
And where the project suits, that is always my preference.
But...
I meant the weight.
(I'll be watching these amazing talks until it arrives) https://twitter.com/jamstackconf/status/1448278346996011013
(I'll be watching these amazing talks until it arrives) https://twitter.com/jamstackconf/status/1448278346996011013
@remotesynth 100% agree!
Perhaps I should write a 2021 version of this article.
Getting the same workflows for serverless functions as the rest of the site would surely feature!
Perhaps I should write a 2021 version of this article.
Getting the same workflows for serverless functions as the rest of the site would surely feature!
It's nearly 4 years since I write this post!
Since then I've started taking many of these features for granted because we talk more about the new things.
But not everyone is aware of these goodies which are becoming table-stakes... so here's a reminder!
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21
Since then I've started taking many of these features for granted because we talk more about the new things.
But not everyone is aware of these goodies which are becoming table-stakes... so here's a reminder!
https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21
@tlakomy @Netlify That would be against our terms of service and as a result would ultimately be shut down.
Our terms are outlined at the url below, and there is a means to report abuse in the footer of our website.
https://Netlify.com/terms
Our terms are outlined at the url below, and there is a means to report abuse in the footer of our website.
https://Netlify.com/terms