6 entries tagged "react" — 3 posts, 3 links.
This is one of the React links that still earns a place because it explains the runtime model instead of another surface API. Understanding React as a way to describe, schedule, and reconcile UI work ages better than memorizing patterns.
Useful for the site's TypeScript and React writing because it turns framework behavior into architecture vocabulary.
This is an evergreen frontend architecture piece because it names the hard parts of UI work: state, latency, consistency, environment, and synchronization. Those problems do not disappear when the framework changes.
It fits the product-minded engineering theme because UI quality is usually system quality made visible.
This is a useful frontend architecture link because it pushes beyond taste and asks what tradeoffs teams inherit when React becomes the default answer.
It belongs next to the React runtime links, not against them. Better engineering judgment comes from understanding both why a tool works and where it costs too much.