Not gonna lie, writing code in various ways can be more efficient processing time wise, but often at the cost of complexity, or readability or time to code it.
As phones have gotten faster, and depending on what I’m working on, I’ll often take the easier to code and read route than the absolutely best optimized route.
Although there are definitely times you still need to optimize
It’s less about individual developers writing bad code and more about whole inefficient frameworks gaining popularity because of ease of use or deployment
I’d argue that’s true in some cases, for example web apps might work well enough on modern device hardware but they’ll never meet the performance of even mid-tier native apps
Not gonna lie, writing code in various ways can be more efficient processing time wise, but often at the cost of complexity, or readability or time to code it.
As phones have gotten faster, and depending on what I’m working on, I’ll often take the easier to code and read route than the absolutely best optimized route.
Although there are definitely times you still need to optimize
It’s less about individual developers writing bad code and more about whole inefficient frameworks gaining popularity because of ease of use or deployment
Are those frameworks so poorly written they can’t be optimized then? That’d have a pretty substantial impact if widely adopted.
I’d argue that’s true in some cases, for example web apps might work well enough on modern device hardware but they’ll never meet the performance of even mid-tier native apps
Ah gotcha. They’re just inherently less performant in some/many cases but that provides a benefit in some other way.