The thought of a critical revenue impacting API changing dynamically without warning is absolutely terrifying to me. The thing is, no other software in existen

The thought of a critical revenue impacting API changing dynamically without warning is absolutely terrifying to me. The thing is, no other software in existence works like this. Payment systems are ubiquitous across an incredible array of devices outside the context of a web browser and they are perfectly fine with using normal software engineering techniques like package management and static linking. Dynamic script imports are fraught with hangups like http errors and slow user hardware causing race conditions. And you're then always tied to using some kind of loading function. Remember having to write entire applications within a jQuery onLoad? It's a vestigial pattern from the early days of the web. We're better than that on the front end now.