Two notes: one is how much a surgeon need to know about molecular biology to properly work, a construction workers about the concrete chemistry, a bus driver about mechanics and so on. The other is that in the past "frameworks" was just the OS, with accessible sources, easy to be explored and end-user programming in mind. There was some, like Smalltalk from Xerox Workstations (take a look at a modern Pharo demo to see them or this
https://youtu.be/M0zgj2p7Ww4 old commercial demo) or LispM (for instance
https://youtu.be/RQKlgza_HgE to give a bit of eye candy) etc.
Now if students start high level in these systems well, they do learning digging as much as they want a bit at a time, nothing hidden. Instead we have pushed for commercial reasons a gazillion of "isolated layers" of crap just to been able to sell bits a bit more. Do you imaging more realistic today students learning ASM to be run on CPUs now complex enough to have a full OS inside or coming back to a single app-OS-framework like in the past? As a hint: look the evolutionary path from widgets GUIs to WebUIs, from visual menus to search&narrow, NotebookUIs, "prompts" etc.
There will be an immense amount of work to do of course, something that can happen in FLOSS world backed by academia and large research labs, definitively not by some even giant enterprise, but we are anyway going there, the quick we realize the less damage, pain and waster works we will make.