This book is a mixed opinion kind of thing, a lot like the language itself. I think that if you find yourself strangely attached to Perl, you will also experience a strange attachment with this book. It feels as organic and chaotic as the language design and using it as a reference is a lot like using Perl to solve a problem - it's all there, it's just arranged in potentially ridiculous ways.
If you are considering using a printed copy of this book as a reference in this day and age, you should consider other options. Do you refer to printed manpages often? I thought not. Considering the book's notorious organization (notorious lack thereof), the only way you're going to be successful in finding specific language topics in reasonable time here is if you have already read the book a couple of times cover to cover (in which case you don't need my opinion).
However, this is generally construed as one of those good books on programming languages. It has an above average level of detail, it makes for an introductory text as well as a tune-up for the advanced user, but the real charm is how naturally language concepts are explained (even if they're misguided) and the unique insight it gives on the language design resulting in moments of unexpected intuition when using Perl. I think this book is beloved by a rare sort of right-brained geeks - it's too emotional for a stereotypical coolly logical C programmer and too technical and intense for a stereotypical creative think-tank Ruby programmer. It's Perl through and through.