[cnity]

I think we lack the primitives to understand and discuss messy complicated real world frontends. Something about UI state and its coupling to servers, plus time, plus Conway's Law, causes a real messy situation that appears to be much easier to avoid on the backend than on the frontend.

This creates a massive gulf between beautiful simple frontend toy examples and the reality of applications made with those same frameworks when deployed for multiple years and product cycles. I think it is a big part of what fuels shiny framework adoption. You think: "yes, this here is what will resolve the complexity and pains I see in my work codebase", and this is bolstered by your carefully curated personal side projects.

[agos]

I am personally thinking creating an alternative to the ubiquitous todo app to highlight how different frontend libraries/frameworks/state solutions tackle common problems.

One example could be a form where the validation rules of one field depend on another, where you have to pick an option from a list that is loaded from a server (what do you do when the current value is not among the returned list?), etc.