When the project you're working on produces 1MB+ binaries.
IDEs provide huge amounts of convenience. Central to their ability to do so is keeping a large number of data structures in memory that speak to various attributes of the source code at various stages of compilation.
Take a look at the debug symbols for a large binary. They can reach into hundreds of megabytes. Now account for some duplication and indexing of those symbols to support wicked-quick IDE menus and you start to see how an IDE can have such a large in-memory footprint.
It doesn't explain all the bloat, some of it is simply because of schedule pressure and when 'good enough is good enough' held true, but it certainly puts you in the right ballpark!
6
u/GeorgeForemanGrillz Dec 06 '15
Latest Macbook Pro with 16gb RAM. When did 2 gigs for an IDE ever become an okay thing?