Yeah, I'm not sure what IDE they're talking about, but certainly IntelliJ will happily use 800% CPU, causing the fans to spin up impressively, when starting up/reindexing/doing any of the slow things that IntelliJ likes to do.

Glad to learn that the reindexing is multi threaded :)

Yes... and he's trying to say a lot of software out there aren't written multi-threaded because either there wasn't much performance gain or the developers simply choose not to.

Compilation and linting are mostly mono threaded. At least in the languages I use. That is a lot of direct waiting.

> Compilation and linting are mostly mono threaded.

Which languages fall on your list? (Just curious)

I use:

* C (make and gcc can thread)

* Python (no real thread story)

* JS (depends)

* Scheme (usually threads)

C, C++. Compilation can be multi threaded. Linking is inherently mono threaded. A number of optimizations flags are mono threaded (and take very long).

Python. Lint is mono threaded. The virtualenv setup is mono threaded (running requirements.txt).

Java. Mono threaded for package generation (jar files). Not sure about compilation and running tests. Most of Eclipse is mono threaded (last I used it) like indexing and rendering and auto completion.

Outside of that, opening any IDE, tool, application or browser is a mostly single threaded operation. The rendering of most GUI is also single threaded.

> Linking is inherently mono threaded.

This is actually not the case -- modern linkers (e.g., lld) can take advantage of multiple cores.

https://lld.llvm.org/

so can the 'gold' linker.

Interesting -- do you have a link on this?

Make definitely requires a well-specified list of dependencies, meaning that the targets and prerequisites need to specify a DAG from the source files through the intermediates to the final target executable(s). If that's not complete then a threaded make will fail.

Most recursive make systems can't be run in jobserver mode because the graph is not well-specified.