profiler

It comes with a builtin IDE and profiler and everything else, so you just gotta dig in and learn.

But it's definitely not the rule and the speed difference between the one and the other is so small that only a profiler can guide you to optimizations like these.

Anything that harms posthoc reasoning about a program with a debugger/profiler/log can be plenty painful.

Imagine the behavior profiler learning enough to notice trends and even changes in groups.

On Firefox, the profiler tool will show you garbage collection in red.

Doing a couple of passes with Chrome's profiler or React's profiling tools would give you a better idea of where your time is going.

It's a sampling profiler; you shouldn't see a big performance hit.

Go's profiler doesn't have flamegraphs, but it has directed graphs.

And then there are the valgrind tools other than memcheck: cachegrind (cache and branch-prediction profiler), callgrind (call-graph profiler), helgrind (thread error detector), massif (heap profiler), and probably more I forget.

The last thing I need is a behavioral profiler that insists it has determined I'm not me and there is nothing I can do to prove it wrong.

In the java environment I can manage an application container, profiler, debugger, compiler, packager, test suite all from one application.

And nobody has even shown that apriori reasoning is any better than posthoc reasoning (debugger, profiler etc.) Deciding that we must reason completely about our program before we ever run them completely ignores a whole set of useful tools that we have at our disposal.

Use the more capable nvprof command-line profiler instead." IMO there are way too many use cases for the command-line profiler to get rid of it, probably ever.

Lots of good stuff, and some not so good stuff: "Deprecated: legacy (environment variable-based) command-line profiler.

It's good that you're so certain about this, but I can just as easily say "running your program in a debugger and a profiler is the best way for people to think about programs".

Recently however I've started using sampling profilers" pprof is a sampling profiler.

Yes, but C++ enjoys profilers like Instruments, Visual Studio Profiler, Intel Amplifier among many others that allow to check how all that meta-programming is affecting the application, while Haskell tooling is much more limited.