The comment very much does come across as being mad at coworkers for not putting in time after-hours.
All fine, if your contract has the "I am a robot" clause or if you happen to write COBOL for a living. The rest of us will have to learn to stay up-to-date, just like carpenters, doctors or gardeners. Because nobody wants to hire someone who missed all progress since graduation...
I'm not saying that you should never learn anything new. For example, I really hope that I have a chance to ditch C++ and Java both for Rust one day, but I can't just go and do it today and that's fine. Change does not need to happen at the pace that some people seems to think it does.
And yes, I would be pretty irritated to find anyone in my team who thinks there is nothing else for him/her to learn, even in their field of expertise.
I do go looking for libraries when I have a need for some functionality, but I don't seek out new libraries to replace other libraries or my own code when the existing solution works. It's the frequent rewriting of working code to use some new tool/framework/library just because it's new and sexy that I find problematic.
I spend plenty of my own time on math/CS/<techs that I'm personally interested in>, and I think companies benefit from those as they make me a better programmer - but most/all? companies don't really appreciate and never reward those efforts 'cause those aren't the latest fads <sigh>.