4 ms·
These transparency effects have been in macOS, ipadOS, iOS, and tvOS for years though?
by c-hendricks 1y ago
These transparency effects have been in macOS, ipadOS, iOS, and tvOS for years though?
- landl0rd 1y agoThere's a difference between something like a transparent background (you can run i3/picom on a potato) and having to composite many little UI elements to render a frame.
- gmueckl 1y agoI can think of a couple of creative ways to dramatically optimize rendering of these effects. There is probably quite some batching and reordering possible without affecting correctness.
- landl0rd 1y agoCeteris paribus your performance is always going to be substantially worse even with tons of fancy tricks. Those also get much harder to implement when you're building a complete UI toolkit that has to support a ton of stuff rather than just writing first-party apps/OS components.
- gmueckl 1y agoI think that the batching that I have in mind would work especially well with complex layouts. The thing to realize is that even if you have tons of elements on a screen, their visual components aren't actually stacked deeply in most cases and the type and order of applied effects is quite similar for large groups of elements. This allows for pretty effective per-level batching in hierarchies, even if elements don't have the same parents.
- chrisweekly 1y ago"ceteris paribus" - "all else equal"
- landl0rd 1y agoRight. My point is the response to this is "well if we optimize it more we'll improve performance", but oftentimes if you optimized the existing code you would also improve performance. Your end state is still worse.
- gmueckl 1y agoIs it really worse if the GPU spends maybe 0.5ms more per frame on these effects? I'd be surprised if a good implementation adds much more to the per frame rendering time.
- butlike 1y agoThanks. Wasn't familiar with that latin
- blinding-streak 1y agoThe reality distortion field is back, it seems.