
Phil Hawksworth
@philhawksworth •
No turkey for me today.
Instead, I’ll be hosting this.
Can’t wait! https://twitter.com/ItsHumdingers/status/1200028177223110656
Instead, I’ll be hosting this.
Can’t wait! https://twitter.com/ItsHumdingers/status/1200028177223110656

Phil Hawksworth
@philhawksworth •
Delighted to see #JAMstack feature in this list about #webperf technologies to watch in 2020.
Especially since @simonhearne is so thoughtful, smart and thorough. https://twitter.com/simonhearne/status/1199694905691516933
Especially since @simonhearne is so thoughtful, smart and thorough. https://twitter.com/simonhearne/status/1199694905691516933

@rockerest These are the sort of updates that originally brought me to twitter.
More pie status updates please.
More pie status updates please.

Phil Hawksworth
@philhawksworth •
Christmas came early. https://twitter.com/devdevcharlie/status/1199916385075228673

@TitPetric Ha ha!

@TitPetric Nah —
Assembly.
Assembly.

Phil Hawksworth
@philhawksworth •
Fascinating detail and insights abound in this casestudy from @lynnandtonic. All about the latest, and outrageously good incarnation, of her website. (https://lynnandtonic.com/)
https://lynnandtonic.com/thoughts/entries/case-study-2019-refresh/
https://lynnandtonic.com/thoughts/entries/case-study-2019-refresh/

@keirwhitaker Thank Keir! That's most kind of you.

@peduarte @SlackHQ LOL. Yeah. Like we didn't already have enough *fun* with this in CMS land.
https://noti.st/philhawksworth/yUEjmX/i-can-smell-your-cms
https://noti.st/philhawksworth/yUEjmX/i-can-smell-your-cms

@dizzyd I'll drink (a Snake Juice) to that.

Phil Hawksworth
@philhawksworth •
The new WYSIWYG input in @SlackHQ reminds me of when I used to use Microsoft Word and would spend more time trying to undo unwanted automagic formatting than writing the things I went there to write.
This is not the codefence I was looking for.
This is not the codefence I was looking for.

@laurieontech @chriscoyier I'm not so sure that everyone has heard of JAMstack yet... but otherwise I totally agree.

@brendandawes You complete me.

@laurieontech @chriscoyier I agree!
Although I sometimes find explaining that simplicity can be... um... a complicated conversation.
Momentum is a tricky thing. ☺️
Although I sometimes find explaining that simplicity can be... um... a complicated conversation.
Momentum is a tricky thing. ☺️

Phil Hawksworth
@philhawksworth •
"I’ve Had Some VCs Asking Me About Jamstack"
— says @chriscoyier
🤔
He goes on...
"JAMstack is funny. I’m a massive fan. Technologically, it’s both super simple/boring AND a paradigm shift in building websites"
Hard agree!
I ♥️ the power of boring!
https://chriscoyier.net/2019/11/26/ive-had-some-vcs-asking-me-about-jamstack/
— says @chriscoyier
🤔
He goes on...
"JAMstack is funny. I’m a massive fan. Technologically, it’s both super simple/boring AND a paradigm shift in building websites"
Hard agree!
I ♥️ the power of boring!
https://chriscoyier.net/2019/11/26/ive-had-some-vcs-asking-me-about-jamstack/

Phil Hawksworth
@philhawksworth •
This was a good choice. Focussing on our own core competencies and building our product rather than re-inventing logging infrastructure was smart. I’m blown away by what the @Netlify infra team do daily. And what @ry_boflavin and team have built boggles my mind. https://twitter.com/Netlify/status/1199601250637172737

@klarstrup @swyx Yeah, I like that combo.
- Generate a view and URL of every page.
- Progressively enhance with client-side rendering and APIs for content.
In some cases that will be perfect. In others that will be over engineering. In others still, it might not be practical. But I like it.
- Generate a view and URL of every page.
- Progressively enhance with client-side rendering and APIs for content.
In some cases that will be perfect. In others that will be over engineering. In others still, it might not be practical. But I like it.

@sultaninen @swyx There are some wonderful use cases for client-side apps. And we can do more in the browser than ever before. I find that exciting. But indeed, we can also brilliantly deliver most website projects via the web standards we’ve worked so hard to establish. So yeah, it depends. 😌

@eduardoboucas @stackbithq This is wonderful! What a great match!

@jupiterorbit Thanks Kaustav!

@swyx Might also be worth considering some drawbacks:
- robustness principal (If we make js a rendering dependency)
- performance (for first load)
- reach (particularly for underpowered mobile devices)
- SEO (if content not in html)
I’m a fan of both.
I tend to say “it depends”
- robustness principal (If we make js a rendering dependency)
- performance (for first load)
- reach (particularly for underpowered mobile devices)
- SEO (if content not in html)
I’m a fan of both.
I tend to say “it depends”

@Una Lookin’ good, CheeseLords! 😎