Sure, at least now the standards are much more stable than in the 90s (I can't imagine trying to keep up with the rapid and constant platform lock in gotchas between netscape and ie...) but learning all that stuff takes a lot longer.
It is like how you can start a car easier today than you could in 1920. The car is much more complex, but the abstractions built on top of that have made it as easy as turning a key rather than having to rev the engine, crank it up, etc. But anyone trying to be an automechanic is expected to know the fine grained details of the modern combustion engine and all the quirks auto manufacturers use to make them more efficient and performant, or else they don't come off as "professional".
I feel the same way with any development role. It doesn't feel professional if I don't know the whole stack behind it. And the stack, like the car, has only gotten taller. Average Joe can pick up Drupal or jquery + bootstrap + rails and crank out a pretty neat web app, but the second their tools don't cover some use case and they are forced to look at things like the TCP stack, packet headers, http headers, etc, and they look lost, they also look bad at what they are doing.