That 20 MB of space, would mostly be for writing graphics code. All the images, resources, hidden stuff, animations, code to run those animations, etc. Its not

That 20 MB of space, would mostly be for writing graphics code. All the images, resources, hidden stuff, animations, code to run those animations, etc. Its not that the core program has increased in size or has lost performance, but that the code required to build a good program based on that core has increased exponentially. Also, as a developer, I usually don't care much about memory until I complete the program, check if its consuming abnormally high memory and then sit about to optimize. So, the developer for calculator.exe saw that the program consumes about 0.125% of commonly available memory size (16 GB), and probably concluded that its good enough for a program that is opened and closed, maybe 10 times a day. Its the same with processing power. Unless you are writing highly resource hungry systems, losing a few thousand cycles here and there are not an issue. Compounding this problem is the depth of the tech stack and the typical number of stacks used for an application have increased tremendously.