← Back to context Comment by jaffathecake 1 day ago Sure but this is a technical post aimed at a technical audience. 4 comments jaffathecake Reply Telaneo 1 day ago What's the liktlyhood of ~~a technical~~ any audience being 4 days behind on updates? (hint: very high) qingcharles 20 hours ago Not me keeping Chrome open for two months with "New Chrome available" badge in the corner. bigstrat2003 1 day ago None of which means you should expect your audience to have a new version which came out three days ago. Lots of technical people stay behind the bleeding edge for very good reason. jaffathecake 1 day ago This is why I added the wasm fallback. The question was why I didn't serve PNGs to everyone.
Telaneo 1 day ago What's the liktlyhood of ~~a technical~~ any audience being 4 days behind on updates? (hint: very high) qingcharles 20 hours ago Not me keeping Chrome open for two months with "New Chrome available" badge in the corner.
qingcharles 20 hours ago Not me keeping Chrome open for two months with "New Chrome available" badge in the corner.
bigstrat2003 1 day ago None of which means you should expect your audience to have a new version which came out three days ago. Lots of technical people stay behind the bleeding edge for very good reason. jaffathecake 1 day ago This is why I added the wasm fallback. The question was why I didn't serve PNGs to everyone.
jaffathecake 1 day ago This is why I added the wasm fallback. The question was why I didn't serve PNGs to everyone.
What's the liktlyhood of ~~a technical~~ any audience being 4 days behind on updates? (hint: very high)
Not me keeping Chrome open for two months with "New Chrome available" badge in the corner.
None of which means you should expect your audience to have a new version which came out three days ago. Lots of technical people stay behind the bleeding edge for very good reason.
This is why I added the wasm fallback. The question was why I didn't serve PNGs to everyone.