5 ms·
We do more things, and have more complex graphics. Eg, a 320x200x8 display has 64000 bytes of memory. A 4Kx32 bit display has 33177600 bytes of memory. That's
by dale_glass 5y ago
We do more things, and have more complex graphics.
Eg, a 320x200x8 display has 64000 bytes of memory. A 4Kx32 bit display has 33177600 bytes of memory. That's 518 more times memory used just for a single screen. Take into account that these days we have compositors and each window is present in memory on its own, before it's composed into the result, and it's even worse.
We also work on far bigger projects. The project I work on as a hobby has 400K lines of C++. Imagine the amount of processing an IDE needs to do to parse all of that and provide its various convenient functions. And of course a good chunk of that is in RAM, because that's far too much stuff to parse everything every time.
Old tools also don't really cut it anymore. If I try running ctags on it, it comes up with a 14GB tags file. I don't think it handles it quite right.
- andrewmcwatters 5y agoThank you for mentioning ctags, even if it's not useful today. I wasn't aware of this tool.
- dale_glass 5y agoI mean, it depends on what you use it for. My project seems to confuse it in some way. But it should work perfectly fine for a lot of stuff.