I read the 20th anniversary edition. As the preface admits, the book is dated; it does cover some of the algorithms that are still in use today (RSA, Diffie-Hellman, SHA-1, MD5, Kerberos), but it also describes a ton of stuff that has no practical meaning anymore. If you're looking for cryptography as it is applied today, look elsewhere. (The preface suggests Cryptography Engineering by Schneier, Ferguson, and Kohno; I haven't read it yet.)
However, this book is more than an algorithms list, and that's what keeps it relevant. You see, there are a lot of stuff around cryptography, and it turns out to be just as important as the algorithms you pick! The fact that you're using an industry-standard RSA doesn't mean you're safe; it means your security hinges on the security of the key. How do you generate it? How do you store it? How do you transmit it? (Should you even?) How do you rotate it? How do you destroy it? It's not enough to be a skillful builder who picks good building blocks; you also got to be an architect and ensure that the structure won't fall over in a light breeze.
Schneier also lists a lot of broken algorithms. At first, I thought it's a waste of space, but the purpose gradually became clear: he demonstrates why people shouldn't roll their own crypto. He quips that anyone can design a cipher they themselves cannot break, but also provides abundant evidence that most of the stuff that can be imagined can also be broken. From this day on, I'd have a paranoia fit every time I have to combine cryptography-related functions together; you just never know, even if you're a PhD and know everything there is to know.
Finally, and somewhat predictably, the book is still good at explaining basics. As noted above, you shouldn't use them to construct anything yourself, but it at least enables you to satisfy your curiosity and make sense of Wikipedia articles.
I'm not a cryptographer, nor an infosec specialist, so I'm not in a position to give recommendations. But I got some new insights from reading this book, and I certainly got a "map" of cryptography as a field, so there's that.