Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

Not fast enough. Performance is king during development.


sort by: page size:

fast is about development speed, not performance.

I'm not talking about runtime speed or latency, rather about development speed.

They were probably referring to speed/ease of development, not application performance.

It’s a trade off between speed of development and performance. Speed of development seems like a good optimization for an experimental project?

Slow? You mean in execution? You can't mean in development!

I can. It seems developers in general do not consider performance to be a priority anymore, unfortunately.

Because application performance matters more than developer performance.

Most of the time, runtime speed is far, far less important than developer speed.

I guess it’s more that what is developed is lead by product people and those don’t know how to plan for performance issues and instead inadvertently push for more features in a shorter time.

I don't think I've ever worked on an application where performance wasn't a problem. The ability of programmers to write slow software grows faster than computing power does.

> well designed software

Ah, there's my problem. Maybe at some point I'll get a chance to work on one of those.


Developers care more about performance if it's slow on their computers too.

A lot of your article goes on to talk about development time speed up. The original article discussed performance where it is critical, like a game. You can't have compensate on performance even if it comes at the price of higher development time.

Is it always about things being faster? I would take less speed for better integrations and less development time.

not being too slow and "squeeze every last drop of performance possible" is not really the same, and the latter is an expensive tradeoff to make.

Performance is a tradeoff. Sometimes shipping a feature is more important. Sometimes cross-platform support matters more than native speed. Sometimes performance optimizations are a distraction from other, more important, work.

No, because most software development houses prioritize getting something that works over performance wankery.

It's surely a developers' paradise - but what about performance?

I don't think many people spend much time on performance anymore in creation stages. Optimizing performance nowadays is purely reactive, I find.

It's not so much about immediate performance, but about headroom.

The blog post https://www.techempower.com/blog/ puts it better than I:

> I argue that if you raise the framework's performance ceiling, application developers get the headroom—which is a type of luxury—to develop their application more freely (rapidly, brute-force, carefully, carelessly, or somewhere in between). In large part, they can defer the mental burden of worrying about performance, and in some cases can defer that concern forever. Developers on slower platforms often have so thoroughly internalized the limitations of their platform that they don't even recognize the resulting pathologies: Slow platforms yield premature architectural complexity as the weapons of “high-scale” such as message queues, caches, job queues, worker clusters, and beyond are introduced at load levels that simply should not warrant the complexity.

next

Legal | privacy