Agreed
> It took me like 30 minutes
I can tell you didn't need to build it ;)
I find this to be ideal when working with a large codebase. I don't even need an editor with fancy intelligence features and LSP integration; a bare bones vim or emacs paired with a website with all the intelligence already there.
Is this a serious question? Assuming it is, to insert printf statement, or attach a debugger and step through the program and take backtraces to supplement or confirm the information you gather from reading the code.
The OP's scenario is being curious how Chromium does something: so it suffices to find the relevant snippet and then copy it elsewhere. The Chromium code is assumed to be already working and does not need debugging.
To clear myself of any wrongdoing in regards to copyright :) They had a very nice comment explaining how the workaround works, and we used a different image manipulation library, so I couldn't, and didn't, copy it as is.
So not only it was easy to find the workaround in their huge codebase, they also explained it well so I could replicate it in our codebase from scratch.
> The Chromium code is assumed to be already working and does not need debugging.
Even if it doesn't need debugging, debugging features can help engineers understand the code better.
I too was pleasantly surprised how readable it was.