A few months ago Sebastian Aaltonen's modern mobile rendering talk based on HypeHype's new renderer went online. I thought I'd do a quick post with some thoughts, as well as to give myself a handle when cross-referencing from my rendering wiki page.
- One thing to note is that the talk covers not only rendering concerns, but also some general development practices like how to design an API iteratively (in this case, with a focus on performance), and how to clarify goals and support levels by looking at potential customer base to baseline requirements and constraints.
- There is a good focus on what the backend/"userland" split of responsibilities are.
- Lots of patterns that go beyond rendering, like use of handles, allocatores, cold/warm, understanding rate of update/executions, etc. You could very well find similar things in some high-performance network-heavy product.
- Great summary in the small print over in the last section. Avoiding some potential pitfalls, simple single-threaded design that is built with multithreading in mind, focus on time spent "doing work" vs overhead.
Happy rendering!
Tags:
design graphics
Home