[baron816]

The tradeoff isn’t dev job easy vs better performance. The abstractions allow devs to build faster or work on things users care about instead of unobservably better performance.

[drnick1]

Oh, you mean those shitty Web UI frameworks with worse performance on modern hardware than native GUI programs from 1995?

Back then devs were not taking shortcuts, it was the C API or bust, and it very much shows how far we have regressed.

[SiempreViernes]

Oh no, the devs back then were for sure taking all the shortcuts they could, there just weren't as many ways to leave problems for the users compute to solve.

[AceJohnny2]

> instead of unobservably better performance

That's... quite the choice of words there

[SteveNuts]

> instead of unobservably better performance.

It's imperceptible because the hardware has gotten so much faster. This would be like a top fuel dragster the size of a freight train.

The engine is incredibly powerful but the overall performance is hindered by the size of the overall vehicle not being optimized around it.

[alex7o]

The problem Is when the performance problems becomes observable. Only after a specific scenario like low power mode for example

[vlan0]

Which is such a capitalist lens to look at things through. Optimizing for a very small window of reality.

It's the same sort of optimization that drives behaviors where corporations feel no need to contribute to open-source projects. The same projects that enabled those very corporations to exist.