I'm with you on the fact that React is overused, but: > in ~100ms is not, in my estimation, worth the massive extra overhead of using a front-end framework T

I'm with you on the fact that React is overused, but: > in ~100ms is not, in my estimation, worth the massive extra overhead of using a front-end framework The phenomenon of change blindness means a 100ms "blank screen" can be the difference between the user recognizing the fact that they've made an error and getting frustrated because they can't tell where the error is. The 100ms reload means if you don't want that to happen, you have to be much more careful about how you design your errors. It's an easier design problem if the user sees the error appear immediately where their attention is already focused. https://www.youtube.com/watch?v=bh_9XFzbWV8 https://www.youtube.com/watch?v=bh_9XFzbWV8 I'd argue caring about this is more important for a smaller product where the marginal cost of a single user churning is (probably) much higher.