New blog post:
-
Zach Leatherman :11ty:replied to Mario on last edited by
@mariohamann @chris_hayes I usually donāt promise blog posts because the second I promise a post I lose all motivation to write it
-
Zach Leatherman :11ty:replied to Joe Lanman on last edited by
@joelanman a little bit! I know they have their own fork of puppeteer that might have worked nicely here https://github.com/cloudflare/puppeteer
-
Scott Jehlreplied to Zach Leatherman :11ty: on last edited by
@zachleat I'm sure there's a good answer to this but is there a reason SVG isn't supported by opengraph? Seems like it'd be a nice way to point to a composed graphic and avoid these screenshot services (however genuinely cool they are)
-
Zach Leatherman :11ty:replied to Joe Lanman on last edited by
@joelanman fixed, thanks!
-
Zach Leatherman :11ty:replied to Scott Jehl on last edited by
@scottjehl I donāt think there is a *good* reasonājust what each client platform supports? I donāt think the docs take a stance on it: https://ogp.me/
-
Zach Leatherman :11ty:replied to Risotto on last edited by
some prior art here:
https://www.zachleat.com/web/automatic-opengraph/ and https://www.zachleat.com/web/api-opengraph-image/but the TL;DR of it is that I wanted to decouple this service from builds to improve build times
-
Risottoreplied to Zach Leatherman :11ty: on last edited by
-
Zach Leatherman :11ty:replied to Risotto on last edited by [email protected]
@risottobias @baldur the entire service: https://www.11ty.dev/docs/api-services/ though my web sites are probably the top consumers of it
-
Zach Leatherman :11ty:replied to Stuart Langridge on last edited by
@sil ha! incredible parallel
-
benschwarzreplied to Zach Leatherman :11ty: on last edited by
@zachleat if this were Twitter Vercel staff would be all up in replies explaining what happenedā¦ but they arenāt, they never left Twitter.
To me the fact they Vercel and all thier staff were able to look past what X has become for the sake of their hype machine is a bad signal
-
Zach Leatherman :11ty:replied to benschwarz on last edited by
@benschwarz ā¦yeah. It isnāt just Vercelāa lot of the JS-dev ecosystem is that way. Definitely hurt my career when everything split.
-
benschwarzreplied to Zach Leatherman :11ty: on last edited by
@zachleat I can use a boatload more š¤Æ emoji if that helps?
-
Zach Leatherman :11ty:replied to benschwarz on last edited by
@benschwarz the only engagement that performs a meaningful function on mastodon is boost (favorites are for good feelings only)
-
Francis š“āā ļø Gulottareplied to Zach Leatherman :11ty: on last edited by
> Mind-boggling that the same service would use ~1276 GB-Hrs per month on Vercel and ~101 GB-Hrs on AWS. Mind-boggling that the same service would use ~1276 GB-Hrs per month on Vercel and ~101 GB-Hrs on AWS.
This is with all the caching in place, not the same workload hitting lambda, right?
In either case yes mind boggling, and I used to run the team that owned that.
-
Zach Leatherman :11ty:replied to Francis š“āā ļø Gulotta on last edited by
@reconbot yeah, with cachingā71% cache misses on the Vercel side. ~85% cache *hits* from CloudFront.
-
Zach Leatherman :11ty:replied to Zach Leatherman :11ty: on last edited by
Found some stats:
28.8% cache hits on Vercel
81.2% cache hits on CloudFront -
Ryan Townsendreplied to Zach Leatherman :11ty: on last edited by
@zachleat all CDNs are not created equal when it comes to cache eviction.
Yet another thing often selected because of some flashy feature or promise that has knock-on significant impact on origin load and financial implications
Remember folks: the difference between 95% and 90% cache hit ratio is a doubling of origin traffic!
-
Zach Leatherman :11ty:replied to Ryan Townsend on last edited by
@ryantownsend whatās the difference between 90% and 28%
-
Ryan Townsendreplied to Zach Leatherman :11ty: on last edited by
@zachleat bankruptcy.
-
evanareplied to Zach Leatherman :11ty: on last edited by
@zachleat I'm curious if you looked at Google's serverless products. In particular, Cloud Run also has a free tier of a similar size to Lambda, but it makes it easy to run a Docker container of the size you want without having to do the layers thing yourself.
I think the UX is also better, though they expect that you just have a container that answers HTTP, and don't put an API gateway in front of it (no API gateway charges, though).