Here's what I can think of off the bat:
- Handling fonts. A whole world of hurt. Not all of this can be offloaded to OS libraries.
- Handling layout. Another world of hurt. Especially given that many formats have their own quirks.
- Handling complicated things like math and svg.
- Understanding HTML (for formatted paste and save-as-html to work)
- Understanding PDF
- Canvas for the shapes and stuff
- Codecs and stuff for images and video
- General rendering/compositing code
- Accessibility code
There's a LOT that goes into building software like this.
I worked on Microsoft Office as an intern once. The codebase is huge. Build times would be forever without artifact builds. I currently work on browsers, which are in the same situation with a lot of not-immediately-obvious costs.
Layout is in every modern game engine as UI and is even more powerful. See scaleform for example.
Math... isn't in a game engine?
HTML/PDF and other formats? Please how about DXT1-N texture formats, crunched textures, scene descriptions, meshes, animation rigging, etc. HTML and PDF are small in comparison.
Yea I'm not going to continue. What you may not have realized as a MSFT Office intern is that just because it was slow and awful, it might not have necessarily needed to be.
It's not just Office. It's also the two browsers I have worked on (a word processor in particular has a lot in common with a web browser, but it also needs to deal with authoring). There are many things that need to be done that aren't immediately obvious. Sure, a graphics engine has such costs too but it's hard to compare unless you're well acquainted with both sides.
That being said complicatedness has little to do with compile time now, has it? :)
There are some articles of Joel Spolsky explaning why office document formats are so complicated (not my word) [1]. The spec for MS doc is like 500 or so pages. The spec is longer than my video game graphics book I had in college. I recommend some research before assuming.
> That being said complicatedness has little to do with compile time now, has it? :)
Actually there is a correlation [2]. Of course it depends on what you call or think complexity is.
Believe it or not engines may not actually be as complex because they typically are based on math formulas or combinations of simple algorithms. Math is often simple and doesn't require lots of branching (if conditions). The algorithms have to be fairly simple anyway otherwise performance would be bad.
Buisiness software or actual video games on the other hand are full of branching. NetHack may not have 3D graphics or any graphics but it is an extremely complicated game.
[1]: https://www.joelonsoftware.com/2008/02/19/why-are-the-micros...
edit: I noticed you typed make. Do you perhaps mean make -j 8 or something (depending on core count)