Are you telling me a readonly property is wrecking my performance?
Summary
The piece reexamines a UI performance issue where auto-scrolling to the bottom triggers frequent layout calculations. The author demonstrates that scrollHeight is not static and can incur cost when messages stream in, and suggests avoiding per-update reads by using a large bound or caching calculations. It emphasizes that properties labeled 'readonly' can change under the hood and that developers should measure and design around layout updates.