And then the whole solution dies because it's slow and not scalable due to the hot reloader plus number of users.
A CDN is pulled in holding a list of changes or something, adding yet more complexity that could have been avoided using a performant caching web server in the first place, and a properly implemented hot reloader.
(Well into millions of requests.)
How did you arrive to the conclusion that our Machinist (the protagonist in this case) would use this go live? Very interested to know if something about the conclusion pointed you in that direction.
A CDN is pulled in holding a list of changes or something, adding yet more complexity that could have been avoided using a performant caching web server in the first place, and a properly implemented hot reloader. (Well into millions of requests.)
Naivete is not well rewarded on the web.