React/JSX reads better than other framework templating because
1. It's easy to differentiate the composed DOM from JS logic, since any logic is expressed in JS rather than mixed into the JSX DOM.
2. JSX maps directly to the JSDOM API.
If you know vanilla JS, JSX is a low overhead abstraction.
Except it only has a query-based cache, rather than a normalized cache by type name and ID. This means a deeply nested component running a mutation to update an entity can’t update the state of a component a few levels up purely with the response to that mutation, it instead needs to invalidate the cache and cause the parent to requery, much less performant.
An improvement might be to make milk type the first choice, and limit the cheese options based on milk type selection. Or maybe just combine both into a single selection with milk type option groups.
I feel like that's giving them too much credit; this is more of a flukuisition. Being in the right place at the right time when your acquisition target implodes.
I guess Sierra Nevada was a big influence early on, and since then I’ve come to appreciate a large variety, from more hoppy offerings from the likes of Russian River, Lagunitas, Stone and recently Almanac, to lagers from Pacifico and Dos Equis, several prominent Belgian brands, and some local sours. I enjoy a wide variety, but always thought of Anchor Steam as bland, malty, and mediocre, on the same low level as Fat Tire, to name a comparable brand.
That said, I’ve only had it bottled, never on tap.
A shame they weren’t able to adapt to modern beer tastes. As long as I can remember, I've thought of them as the mediocre beer I’ll begrudgingly drink only if all other options are exhausted.
You can often use route params or location hash for communicating state sideways if shared context is overkill, with the benefit of making the state bookmarkable or accessible in the history.
If you know vanilla JS, JSX is a low overhead abstraction.