@t3dotgg I had the same criticisms a few years ago, and I have many values inline with Rich. But practices have improved over the years, and there is great opportunity here.
Just one example: check this little demo of how @eleven_ty is doing web components nicely
https://twitter.com/eleven_ty/status/1575598000994279424
Just one example: check this little demo of how @eleven_ty is doing web components nicely
https://twitter.com/eleven_ty/status/1575598000994279424
@dletorey @RockChoir @LondonMarathon Don’t stop me now.
This is me.
Dreams.
Shine.
I wanna dance with somebody.
Boogie wonderland.
This is me.
Dreams.
Shine.
I wanna dance with somebody.
Boogie wonderland.
Singing with @RockChoir at the @LondonMarathon today. Amazing atmosphere and fleeting (but heartfelt) connections with so many runners as they battle on through mile 18.
@FakeLauraLouise @bitandbang Yes! I hunt for videos of people saying their own names in intros, and if in doubt, ask.
@kaelig @eleven_ty Ha ha ha. Don’t tempt me.
Add: deploy an incremental build.
Subtract: serverless function uses api to rollback deploy.
And users learn a little patience along the way.
This is all fine.
Add: deploy an incremental build.
Subtract: serverless function uses api to rollback deploy.
And users learn a little patience along the way.
This is all fine.
This demo makes me unspeakably happy https://twitter.com/eleven_ty/status/1575598000994279424
You weren't imagining it.
Builds are faster now.
https://www.netlify.com/blog/up-to-40-faster-build-times/
Builds are faster now.
https://www.netlify.com/blog/up-to-40-faster-build-times/
@Igloczek @remotesynth @stefanjudis @timbenniks SSR is more slippery because it's not a very definitive term.
It might be in an active server (not Jamstack) or it might be delivered via an Edge Function instead (Jamstack?!)
I think of SSR as at "runtime rendering not on the client", but my campaign for RRNOTC has gone badly
It might be in an active server (not Jamstack) or it might be delivered via an Edge Function instead (Jamstack?!)
I think of SSR as at "runtime rendering not on the client", but my campaign for RRNOTC has gone badly
@Igloczek @remotesynth @stefanjudis @timbenniks Take http://app.netlify.com. That's a React front-end served statically from a CDN. It's Jamstack. But it makes very heavy use of APIs to drive the content and state of the UI. The services and infra delivering that API are very not Jamstack.
And different teams build each.
And different teams build each.
@Igloczek @remotesynth @stefanjudis @timbenniks Oh I see.
I'd say that an application providing an API is unlikely to be built as Jamstack. (unless read-only, perhaps)
But it might be *consumed* by a Jamstack site and be part of the Jamstack ecosystem.
I'd say that an application providing an API is unlikely to be built as Jamstack. (unless read-only, perhaps)
But it might be *consumed* by a Jamstack site and be part of the Jamstack ecosystem.
@Igloczek @remotesynth @stefanjudis @timbenniks I don't fully understand your question in this tweet. Can you help me make sure I don't misunderstand and botch my answer? :)
@timbenniks @Igloczek @remotesynth @stefanjudis I don't want to have to maintain an origin server as part of the infra / logic that I need to service a request.
I want to abstract that away.
There will be an origin server.
I never want to need to consider it.
Like serverless. There are servers, but not in my mental model.
I want to abstract that away.
There will be an origin server.
I never want to need to consider it.
Like serverless. There are servers, but not in my mental model.
@Igloczek @remotesynth @stefanjudis @timbenniks Server in the meaning of an active application running on some dedicated, shared, or virtual infrastructure that you have to keep "up and running" to service the incoming requests.
@Igloczek @remotesynth @stefanjudis @timbenniks Feels like massive overlaps to me.
I still consider the absence of a server in my problem space as core to Jamstack though. Which might not always be true of composable.
I still consider the absence of a server in my problem space as core to Jamstack though. Which might not always be true of composable.
@remotesynth @stefanjudis @Igloczek @timbenniks We don't know what future tools and practices will emerge which can fit nicely into this mental model, so an attempt was made to reframe this to accommodate that and avoid of always shifting goalposts.