Planning on doing a full #11tyConf Organizer retrospective blog post, but in the interest of transparency hereโs a peek at the conference budget (funded primarily by our Open Collective, prices in USD):
Expenses: $7574.20
Revenue: $4653.79 (Free event, but via sponsors and merch)
Profit: -$2920.41
I haven't dug in enough to have opinions but I am fascinated that this (big! important!) web platform argument is happening via fantastic community-facing blog posts, with a Big Brand on each side.
I guess when they agree they just ship without doing outreach to invite the larger developer community into the discussion. Which, I don't know, probably โ usually โ that's for the best. Usually.
A web designer has talent in visual design and UX, and knows the basics of HTML & CSS. If they were going to learn one thing about JavaScript to help what they do, what would it be?
The number of times I have audibly gasped this morning learning about inefficiencies in Next.jsโ <Image> component has made me realize that Iโm a little out of shape.
The hardcoded list of srcset breakpoints kills me. You're taking an image, asking Cloudinary to resize it to w_720, and then downsizing it to 256w, 384w, and 640w (fine) but then serving it, as-is (at least they don't upscale!), under different URLs, as the 750w, 828w, 1080w, 1200w, 1920w, 2048w, and 3840w versions. Lots of useless load events, cache entries/misses, & WILD .naturalWidths result.
I'm glad they give you a per-component way to specify sizes (via imageSizes), and they try to explain it in the docs, but I wish they did more to help here (especially in lazy contexts), because this is the hardest problem in respimg.
I'm not sure why they are always setting decoding=async but whatever can't hurt lol.
I think we're focused on the wrong thing when we look at what tech works for a company like Amazon or Facebook or Netflix.
We should be looking at what tech works when you don't have a small army of staff engineers optimizing it. I want to know what I can scale without paying someone a half million dollar salary to do it.
There should be more case studies on things that don't have a billion-dollar company propping them up, humming along quietly on a cheap-ass VPS somewhere.
@zachleat@collinsworth I feel like I'm gonna spend my whole career wondering if, instead of making supply more complex/expensive, we could somehow grow demand for cheap simple things
Come for the fun, interactive examples, stay for the extensive set of thoughtful, detailed use cases. โAn Interactive Guide to CSS Container Queriesโ by @shadeed9
@simevidas@meduz@db Right, sizes is there to give a value before layout that's a hint of the after-layout width. If it changes after layout, you could get double-loads, which defeat the whole point.
Is the concern what the platform can do for users when authors make the mistake of omitting CSS, like this? Or is there an unmet use case around "HTML-only" responsive images, that you think is important?
@simevidas@meduz@db I'm not sure if this is fixable soon, in a web-compatible way. Some images (like the one you found) are depending on the intrinsic size, and folks might be surprised at some new whitespace / consider their layouts "broken".
I'm doubting that the fix you mentioned will fix this, because it depends on other CSS, and srcset selection can't depend on any CSS. I guess this will end up like 1em meaning different things in different contexts?