The real world is analog, so interfacing to that will never go away. And there are times when the "digital" level of abstraction just doesn't hold, even inside a "digital circuit."
True story: I joined a huge company as an analog chip engineer. But on day one they loaned me out to a digital team that couldn't figure out why their circuits were failing because I actually knew how to drive analog tools and I was the least valuable analog guy being "the new one." I found the problem, learned enough VHDL to fix the circuit the idiot compiler generated and rather than being returned to my analog group I got caught up in figuring out why their clock distribution network wasn't working. It took a couple of years to escape doing "analog" tasks for a digital group and I had to quit the company to get back to doing what I wanted to do and not what the company wanted me to do. (And yes, I turned down some pretty hefty raises and awards the company offered to get me to stay, but while what I was doing was considered analog by digital guys, it wasn't real analog design and I wasn't happy doing what I was doing. If I'd been in the group I had originally been hired for I would have been happy, but the digital group had more influence up the chain of command and wouldn't let me switch.)