I’ve digested more of your post its various links (I’ve worked my way through a bit of Fred H’s blog but had yet to get to that one) but in particular I’d like to respond to the aforementioned link about the core team’s take on hot code reloading.
I understand their rationalization but the problems associated with hot code reloading seem on par with—if not even easier to reason about—zero-downtime-deployments involving structural DB changes in any language’s ecosystem. It seems like a hot code deploy is max two deploys whereas some DB migrations could be get to five or more deploys with a larger blast radius codewise.
Again, I’m new and might not have the whole picture.
I would also like to acknowledge that I do realize I’ve been conflating hot code reloading and general deployment wishes in my posts.
Edited to add: Wellllll ok, if you had to treat every deploy this way, I could see it becoming a burden.
