For games, it's not a 'culture', it's because games become very frustrating to play when non-responsive in anything fast paced, and thus will review badly and become 'not fun' and thus will not sell. It's directly connected to sales metrics, which is why management in game companies give space for it, and why CDPR recently offered refunds for a game because of bad perf on the PS4 tier of consoles, which is fairly unprecedented. You'll notice worse performance in slower paced games typically, such as Civ 6.
Also I've worked on trying to improve swift build perf and have worked on large C++ codebases before. The reason why C++ is slow to compile typically is because templates cause an explosion in code generation, everyone uses boost & the stdlib smart pointers & containers, which all template heavily and result in slow build perf and large binary sizes. Swift & rust do that, often implicitly and in an invisible to the programmer way and type inference are the typical reasons why it is slow and they too, create large binaries. When I started running into swift's build problems, I internally said to myself "oh boy, it's C++ again" and if you go to WWDC and talk to Xcode's engineers or swift compiler engineers, they often call swift 'new c++' and other not as nice names. Swift and rust are also incredibly complicated languages with a lot of edge cases when you start getting into the weeds, on par with C++.
Why are these languages using features such as type inference, stricter and more complicated type systems along with heavy templating? It's because now computers are fast enough to provide these 'developer ergonomics' and 'multithreaded memory safety without locks' that these features become viable in the compilers of today vs. the compilers of yesterday. If they could deliver such abilities in the past without having a compiler that takes too long, they would have. In the past C++ was known as a slow compiling language, like swift is today. You also notice slow build times in other 'statically sophisticated' languages such as scala or haskell.
Golang was specifically designed as a language to provide fast compile times. When they were designing the language, if they had to decide between cool language feature and fast build time, they chose fast build time.
Try to expand your horizons, just because you like something, it doesn't mean most people like it. I wish most people liked performance improvement work.
