3 ms·
He goes on to complain about precursors to compositing. By the late 1990's Linux supported tear free with lower latency than compositors currently support. An
by hedora 4y ago
He goes on to complain about precursors to compositing.
By the late 1990's Linux supported tear free with lower latency than compositors currently support.
Anyway, computers have been getting worse at output latency since the mid 1980's. Compositing is just yet another ratcheted performance and usability regression.
- zozbot234 4y agoLate-1990s systems supported practically tear-free updates for most practical uses, but AIUI there was not enough memory bandwidth for whole-screen updates to be tear-free, especially at higher resolutions and color depths. This is what Carmack is complaining about here. Even then, there are better and worse ways of coping with limited video memory bandwidth, and what's "best" depends on the given application.
- hedora 4y agoAccording to Carmack (in 1995), tear free compatible PCI bandwidth was just starting to hit the market. This matches my memory of configuring tear free before y2k. I know for sure that I had tear free working at 1600x1200x24 (or 16?) by 2001.
- mananaysiempre 4y agoFWIW, the Plan 9 window system is in fact a (very barebones) compositor in modern terms, in that it (unlike classic X and like Wayland) maintains a backbuffer for every (top-level) window instead of communicating “damage” back to applications. That seems to be its very thing—there’s a distinct feeling of “look what computers let us do now” in the papers. I don’t think it knows anything about the widgets inside those windows, either (again unlike classic X and like Wayland). (On the other hand, like classic X and unlike Wayland, it makes the client funnel every drawing operation through the window system.)
- wnoise 4y agoX also had "backing store", but there were reasons it was not very useful in practice.