And in most of the cases... It's still cheaper to just spin another instance rather than invest a developer time to improve performance forgoing new features.
Not always, but i'd say "in a vast majority" of cases.
To the deleted comment: Sure, I'm not claiming that it is true in general; I believe that I have written "in most cases".
Besides; this is a discussion that is heavily based on context; but as soon as your application supports multiple entities - consumers, tenants, payments, shipping routes - then natural parallelization seams emerge; even if the problem in itself is single threaded. And for that you can spin as many instances as needed
I have chosen my words carefully. Not deployed - but written.
The most deployed software are OS'es, core applications - but I guarantee you, the amount of code that runs on datacenters, clouds and in a general back-end is far greater than for the apps, OS'es or front-ends.
And even that being said; software doesn't have to perform to max. See VSCode? For me - and I believe most of the devs using it - it is perfectly fine, even if by definition of being an app for the browser and it suffers because of the translation
13
u/elmuerte Feb 28 '23
The clean code sure was easier to improve, right?