@DasSurma @Jack_Franklin @jaffathecake Yeah of course.
And I also understand exactly how VC funding works and is paid directly to me.
All good.
I might even spring for crisps.
And I also understand exactly how VC funding works and is paid directly to me.
All good.
I might even spring for crisps.
@Jack_Franklin @jaffathecake @DasSurma I think it’s £1 a pint at ‘spoons tonight. So I’ll get the first 53 million drinks.
Feeling really rather smitten with the gorgeous iconography in the new JAMstack page on the @Netlify site.
(And there is really good info there to boot!)
https://www.netlify.com/jamstack/?utm_source=twitter&utm_medium=newjam-pnh&utm_campaign=devex
(And there is really good info there to boot!)
https://www.netlify.com/jamstack/?utm_source=twitter&utm_medium=newjam-pnh&utm_campaign=devex
@bitandbang @seldo ...on the other hand, the term can be confusing if closely scrutinised. (You don’t *have* to use JS or APIs, and “stack” is a nod to the runtime moving from server to the browser with JS).
Naming things is so hard, but having a name helped to point at a set of useful patterns.
Naming things is so hard, but having a name helped to point at a set of useful patterns.
@bitandbang @seldo Yeah I can see this. On one hand, the term JAMstack helped me describe an approach to big brand clients who previously reacted badly to “serving everything as static assets and using JS and APIs with PE to enhance where needed”. That was cumbersome and had loaded language...
Huge kudos to the @letsencrypt team for rapidly collaborating with Netlifyers to help mitigate this.
https://community.netlify.com/t/lets-encrypt-certificate-revocations-3-4-march-2020/9945 https://twitter.com/Netlify/status/1234970055760199686
https://community.netlify.com/t/lets-encrypt-certificate-revocations-3-4-march-2020/9945 https://twitter.com/Netlify/status/1234970055760199686
Wow. You are all great people. ❤️ https://twitter.com/philhawksworth/status/1234908754581295105
Heartbroken for my wonderful @Netlify colleague who lost his home in the Tennessee tornado last night.
Thankfully not seriously injured, but @hazards_of is such a generous person and as member of the support team does so much for others.
Let's help. ❤️
https://www.gofundme.com/f/netlifolk-for-the-padiernos-family
Thankfully not seriously injured, but @hazards_of is such a generous person and as member of the support team does so much for others.
Let's help. ❤️
https://www.gofundme.com/f/netlifolk-for-the-padiernos-family
@denicmarko @scriptconf @youyuxi @marcysutton @simona_cotin @andrestaltz @FischaelaMeer @devdevcharlie That one was a blast!
Good times :)
Good times :)
RT @DavidDarnes: Building a @Netlify Build Plugin: https://david.darn.es/article/2020/03/02/building-a-netlify-build-plugin/
@JonSpeek These are GOLD! I like using @alfredapp, but only tap into a small part of its potential. You're inspiring me to up my game!
More please!
More please!
@TejasKumar_ @ScribblingOn Well shucks! You, my friend, are undoubtedly one of the good ‘uns!
You put a big smile on my face with this thoughtful surprise birthday gift. I’ll get plenty of practice to improve my technique with this apparatus over the next month. Big thanks! 😘
You put a big smile on my face with this thoughtful surprise birthday gift. I’ll get plenty of practice to improve my technique with this apparatus over the next month. Big thanks! 😘
@_baxuz @kentcdodds @sarah_edo I know of business built on offering the skills to manage your assets into a CDN. The unknown landscape upstream can make it very nuanced and tricky.
By removing the moving parts at request time, you open up great automated caching and serving possibilities.
By removing the moving parts at request time, you open up great automated caching and serving possibilities.
@_baxuz @kentcdodds @sarah_edo Thats' a great question!
Caching is hard. Especially when there are many servers or layers in the infrastructure. Setting rules for what gets cached vs what needs to be fresh, and how to invalidate and update on changes is tough.
Ability to cache everything per deploy is a win!
Caching is hard. Especially when there are many servers or layers in the infrastructure. Setting rules for what gets cached vs what needs to be fresh, and how to invalidate and update on changes is tough.
Ability to cache everything per deploy is a win!
@ojrask @sarah_edo @benbyford @joeflateau (The caveat to that of course is that some services might be a company's special sauce, and where they differentiate. Nothing to stop us specialising in our specialism! Often then, its good to build those as an API anyhow)
YMMV
YMMV