@BerkhanBerkdemi @gitlab @Netlify But there was an excellent gif... so we it's not all bad. 😆
Lovely detail in that article Thanks for sharing it!
Lovely detail in that article Thanks for sharing it!
@zachleat Probably a better choice of words. And I'm not suggesting that there is no web server in the stack, more that the web server is not part of your problem space in this model as its job is handled for you automatically. Like how there are wires in wireless and servers in serverless
@jdlrobson Yay! Hello stranger! I'll be there for the first day and evening. Would love to see you.
@bhenbe @Netlify @vuejs @contentful @GoHugoIO @forestryio @NetlifyCMS There is certainly no silver bullet or single solution for all scenarios. But what you describe sounds like it could comfortably wear the #serverless or #jamstack label. Each case needs considering on its own merits, but often, previously accepted complexity can be designed away.
@Marcus_Noble_ The talks were recorded, but I'm not sure what the timeline is for posting them. When it happens, both @render_conf and myself are likely to shout about it.
@Eastmad Thank you sir. And good eyes. I'll fix that to point at http://staticgen.com as it should.
@DavidDarnes @StuRobson @Netlify I better. I brought 4 packs.
Expecting to be VP of Crumpeteering by close of business.
Expecting to be VP of Crumpeteering by close of business.
@mirshko @drewm aaaah! Ha ha ha!
I should kill that, as it has caught me out in the past too... but I like to keep it around for the sake of the demo. Find your way back to the greeeeen (and the master branch) via https://www.hawksworx.com/gimme-gimme
I should kill that, as it has caught me out in the past too... but I like to keep it around for the sake of the demo. Find your way back to the greeeeen (and the master branch) via https://www.hawksworx.com/gimme-gimme