News for hackers. Stuff that matters.
Re:Ranges, Code Quality, and the future of C++ by IshKebab on Wednesday December 26, 2018 @06:37PM (#18765842)
This just doesn't work for making fast software in my experience. It's very rare that 90% of your execution time is in 10% of your code because that code is obvious low hanging fruit and will have already been optimised.

Selective optimisation of hot code will always lead to execution time being spread evenly through your code.

Re:Ranges, Code Quality, and the future of C++ by pjmlp on Wednesday December 26, 2018 @06:42PM (#18765883)
My experience replacing software 100% written in C++ by a mix of JVM/.NET + C++ shows otherwise.

Most of the time, the C++ help isn't even necessary anymore, unless the systems were doing some GPGPU stuff, real time audio or high performance graphics.

Re:Ranges, Code Quality, and the future of C++ by IshKebab on Thursday December 27, 2018 @05:53AM (#18768796)
That's just because Java and C# (or whatever) are fast languages. C++ is only a little faster. Try it with Python or Ruby.
Re:Ranges, Code Quality, and the future of C++ by pjmlp on Thursday December 27, 2018 @07:06AM (#18769005)
From my point of view Python and Ruby are only worthy of shell scripts, and scenarios where performance isn't even part of the requirements list.

Using them in scenarios where performance matters is the typical everything looks like a nail.

Feel free to disagree, my experience during the early 2000 with Tcl has taught me to never use languages without native support for JIT/AOT toolchains ever again when performance matters.

Anything related to distributed computing, performance does matter.