@marcysutton @scriptconf Sad that I missed the chance to say goodbye. Wonderful to see you again, Marcy. I hope the mountains are good to you. Safe travel home.
Until next time!
@buckdoyle @travisci Rather embarrassed to have missed @travisci off my list of resources. Worthy of your attention if you enjoyed my talk at #scriptconf
Just enjoying a bottle of HTM Ale after an excellent day at #scriptconf.
Hoppy and punny. Just as I like it. http://ift.tt/2FYGuxV
Hoppy and punny. Just as I like it. http://ift.tt/2FYGuxV
Nothing to see here at #scriptconf. Just @devdevcharlie controling devices *with her eyes* and *with her mind*!!!
Fascinating way to end a great day.
Fascinating way to end a great day.
Thanks for listening #scriptconf! My slides about infrastructure and #jamstack are now available online for anyone wanting to take a peek -
https://www.hawksworx.com/talks/scriptconf
https://www.hawksworx.com/talks/scriptconf
@jaffathecake So good. Lots of gems in there, but I particularly like that Fergus McContrary's Medium post is a 126 minute read.
@chris5marsh @csswizardry @Documentally Try to get a good night's sleep but also try to have at least one end-to-end run through while standing (not sitting in front of your laptop).
Don't be afraid to look out at the audience as you get comfortable, and most of all enjoy yourself.
It will be ace!
Don't be afraid to look out at the audience as you get comfortable, and most of all enjoy yourself.
It will be ace!
@slsoftworks @KTamas @FischaelaMeer @simona_cotin I'm sure that there will be no technical hiccups at all actually.
WAIT. I DID IT AGAIN.
WAIT. I DID IT AGAIN.
Easy. I'm just popping to the shed to make a dozen. https://twitter.com/awkwardgoogle/status/953329550003523586
Understanding the joke in this tweet is now table stakes. https://twitter.com/ianfeather/status/953923989570801665
@nsteinmetz @biilmann @Netlify @GoHugoIO @getgrav @scaleway That's curious. Irrespective of browser caching, was this the 1st time you'd hit the site after a deploy? The 1st request for a site after its deployment will have slightly slower response time as it will prime the CDN cache via a request to the origin. Then things get faster.
@whymclovin @Netlify Sure! Interested in hearing anything on the perf benefits of generating a view on demand rather than ahead of time. I guess targeted content rather than perf gain?
FWIW, when just a few pages need to by "dynamic", I invisibly proxy those to that service - https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
FWIW, when just a few pages need to by "dynamic", I invisibly proxy those to that service - https://medium.com/netlify/10-netlify-features-to-surprise-and-delight-225e846b7b21#7007
@whymclovin @Netlify If you mean rendering views on the server at request time, then no. We believe strongly in the power of the #JAMstack and removing that complexity.
Powerful automation and reduced friction for timely *pre-rendering at build time* (not req) time is where our power comes from.
Powerful automation and reduced friction for timely *pre-rendering at build time* (not req) time is where our power comes from.