Μας τα έχετε κάνει μπαλόνια. Just pick a name already. Grid's been out for what, 14-15 years now? Ship it as grid-whatever and noone would care. We care about the feature.

Out of curiosity, how do you handle the private cache in Vercel for tenants that don't fit in one server? Do you coordinate revalidation for each instance? With skew protection you must have multiple instances for your smaller tenants as well..

Yes, I should have mentioned that as well. We don't store soft tags at all for the same reason. So no revalidatePath for us, but it's not a big deal for the apps we're building.

So what you're saying is that if we already are caching in our data layer, we could just skip the local cache entirely and use "use cache" only as a directive/signal to Next.js about what/when to pre-render? That's actually... damn 🤯

I agree. For example, we're using "use cache: memory" extensively for heavy computations or some things that are not tenant-specific, like "what's the date in X timezone". We've forbidden the use of cacheTag there though.

As soon as you introduce 2+ instances of your server, don't all of these stop making sense? I mean, how do you even revalidateTag a local or private cache anymore? Everything becomes a remote cache then, doesn't it? I mean the tag manifest *has* to have a single source of truth.

Drop to 120Hz. Anything above that causes the exact issue you're describing. discussions.apple.com/thread/25580...

done

"why us" section in www.webhotelier.net

tailwindui.com was recently ported to Tailwindcss v4. The following 3 screenshots are from Safari 14, 15, and 16 respectively. Safari 16 was released just 2 years ago... There is *nothing* in the CSS that is not supported in Safari 14 other than the fact that it is wrapped inside @layer. 😮‍💨

The point is that people don't always upgrade their OS. For whatever reason. And since Safari versions are tied to OS updates, we'll keep having this problem. Hence the comparison to MSIE.

There is this guy at work that has never upgraded iOS because he believes Apple will nerf his phone's battery/perf.
🤷

That was my expectation as well, however it doesn't. It always generates @layer and @property statements because they are not "polyfillable".

Requiring @property is a showstopper for us. That means Safari 16.4 or later. In other words, say goodbye to 8% of the web population.

First time I've felt "Safari is the new IE" as much.