The irony here is that programming languages and their native APIs are (apparently) not considered part of the stack™ and must be kept away as far as possible from the hands of developers, since this introduces the danger of injecting knowhow.
Not discounting the necessity of mastering the language to be a strong engineer. However the framework being used is just as relevant, if not more so, than the underlying language
A web framework is often a one-size-fits-all solution designed to handle a variety of use cases, some of which conflict with each other. Like a swiss army knife, it does everything but none of them particularly well.