To reduce "the boring revolution" to a React aversion is a bit dismissive. "Boring" is malleable. If your team is full of React experts, React is boring. If y

To reduce "the boring revolution" to a React aversion is a bit dismissive. "Boring" is malleable. If your team is full of React experts, React is boring. If your team is full of backend-oriented engineers who rarely deal with the frontend, React is much less boring. "Boring" is also not binary; it is continuous. The mix of technologies in your stack culminate in some arbitrary measure of boringness. This measure can also be thought of as the degree to which teams choose cutting/bleeding edge technologies. If the mix is mostly cutting/bleeding edge, it's very likely that production support is not boring, and problems operating the stack in production are not boring. Choosing boring technology is also not a panacea that solves every team's problems. Although doing so likely mitigates them.