I've been thinking about a concept that I'm calling "building up vs buiding down". Building up is adding abstractions. Building down is dropping down to the low

I've been thinking about a concept that I'm calling "building up vs buiding down". Building up is adding abstractions. Building down is dropping down to the lower level abstraction to implement something (as opposed to removing functionality altogether to simplify the codebase). I think it's interesting to see people complaining about React: it seems people assume we're always building up and that any complexity comes from using whatever tools we're using. What you did here though is _building down_: you're talking about how the browser deals with the order of script loading and painting, which is decidedly not something that is in the React vocabulary at all, and which one absolutely needs to understand and be able to reason about when dealing w/ client-side state to manage FOUC. The only (minor) complaint I have is that you're framing the knowledge of browser rendering priorities as "tricks" and "tomfoolery". If we want to collectively build better products, it behooves us to understand the technologies we use and when it makes sense to "break" 5 year old dogmas (e.g. the ones saying not to put scripts in <head>).