
slightlyoff@toot.cafe ("Alex Russell") wrote:
The obvious solution is separate, single, read and write phases per frame. Saw it in action recently in a web-experience-inspired system:
The browser's problem is compatibility. We can't begin to enforce this model without developer opt-in as it would lead to tons of obviously broken content. And even if developers opt in, their libraries will have been written for the earlier era of non-pipelined execution.
This has killed many previous attempts.