Angular's Lazy Resource Design Evolves After Community Pushback and RxJS Insights

A developer recently proposed a 'lazy resource' feature for Angular that delays data loading until something actively reads it, rather than loading eagerly by default. A contributor named wartab challenged the initial design by sharing a production implementation where only long-term observers like templates or effects trigger loading, not plain reads. This conflict between two working but opposing rules prompted further design iterations, including separating read intents into distinct entry points such as peek() and toPromise(). However, building out the multi-strategy model exposed hard-to-defend edge cases, particularly around resources that could never return to sleep after a single imperative read. The author ultimately translated the problem into RxJS terms, drawing on its decade of production-tested patterns around hot and cold observables to find a more defensible model.