Relax, my personal experience won't affect the popularity of that profiler.
I am working full time on open source research, so will see when I have time.
If nobody noticed it before, I am probably not using it correctly or I am expecting something different from it.

So to clarify, if I run a script with the profiler that takes 2 minutes for example, it should point out which parts of the code take the most time
And it should not be possible that one part takes for example 10% of the real time, but the profiler doesn't picks this up (that's something I observed).

And just to confirm that I use it correct:
perl -d:NYTProf script.pl
nytprofcg
kcachegrind nytprof.callgrind