> Yeah, all this concern with scalability, portability and clean code, has created quite a dystopian software world.
All of these three - when interpreted reasonably - coincide and even constitute performance improvements:
* You make less assumptions, including regarding the speed of things, when you make your code portable.
* When your code is clean, it's easier to generalize speed benefits rather than when you need to apply some ugly spaghetti hand-written optimization in 20 places.
* Scalability means scaling up, out but also _down_ from the machine you're currently using. How else would you run your, say, distributed search web app on, say, a cluster of RPi 0's?
... Of course, if your approach to scalability and portability is to stick things in a container or vm, and manage a fleet of those, then yeah, that's kind of a problem.
All of these three - when interpreted reasonably - coincide and even constitute performance improvements:
* You make less assumptions, including regarding the speed of things, when you make your code portable.
* When your code is clean, it's easier to generalize speed benefits rather than when you need to apply some ugly spaghetti hand-written optimization in 20 places.
* Scalability means scaling up, out but also _down_ from the machine you're currently using. How else would you run your, say, distributed search web app on, say, a cluster of RPi 0's?
... Of course, if your approach to scalability and portability is to stick things in a container or vm, and manage a fleet of those, then yeah, that's kind of a problem.