For the use cases outlined in the OP, a 36% performance gain for an optimization that complex would be considered a waste of time. OP was explicitly not talking about code that cares about the performance of its hot path that much. Most applications spend 90% of their runtime waiting for IO anyway, so optimizations of this scale don't do anything.

▲

satvikpendem 3 days ago | parent | next [-]

Adding a few borrows and annotations is not "an optimization that complex"; use Arc at first but then find those bottlenecks via profiling then fix them.

	▲	3uler 3 days ago \| parent [-]
		Fix them if needed, the OP’s point is that for a lot of applications it is not needed. For most cases you will still be comfortably in the JVM/golang performance window. Rust is great language, fighting the borrow checker sucks, don’t do it if you don’t need to.

▲

VorpalWay 3 days ago | parent | prev [-]

> Most applications spend 90% of their runtime waiting for IO anyway, so optimizations of this scale don't do anything.

Again, depends on what you are doing. If you are doing web servers, electron apps or microcontrollers, sure. If you are doing batch computation, games, simulation, anything number crunchy, etc: no. As soon as you are CPU or memory bandwidth bound, optimisation does matter. And if you care about battery usage you also want to go to sleep as soon as possible (so any phone apps for example).