Re:“Clean” Code, Horrible Performance
by rileyphone on Tuesday February 28, 2023 @05:56PM
(#34976124)
Not the case if your program is spending most of its time waiting, which is typical these days.
[ Parent
| on HN ]
Not necessarily in the general case. If the program is a single user, locally ran program, then sure. If it's some sort of backend or distributed service, this is just wasted performance that can be used to serve more users. Virtually every distributed service built today is able to take advantage of this.
With a non-pessimal design, not only you are able to pay less money on servers in the long term, you're also able to delay complex scaling strategies. Scaling also costs money.
Not to mention that building something with this kind of overhead also means that a lot developer time was spent in the first place, which is still expensive in our industry.
using 'unclean' code practice will increase development costs. And more importantly - maintainability of such code.
>Virtually every distributed service built today is able to take advantage of this
most of built today services can take much more advantage in using better system design practices.