[bri3d]

Why _would_ you expect anything different to happen at a massive company?

It's not like the team who write the drivers are likely to know of the team working on optimizing compilers, profilers, or anything at all really.

My experience has been that especially in companies working in diverse disciplines across disparate codebases, very little is shared. A team of 8 in a tiny company is just as likely to make the same mistakes as the team of 8 in a bigger company. At large companies with more unified codebases and disciplines, maybe one person or team has added some process which helps identify egregious performance issues at some point in the past. But such shared process or tooling would be really hard at a company like Intel where one team makes open-source Linux drivers while another makes highly specialized RTL design software, for example.

[henrydark]

This reminds me of a line from Great Gatsby, where Jordan says she likes big parties because they're so intimate

[gspetr]

>Why _would_ you expect anything different to happen at a massive company?

Because a massive company has enough money around to put the processes in place and hire skilled people to do both deep[0] testing and system[1] testing.

[0] https://www.developsense.com/blog/2017/03/deeper-testing-1-v...

[1] The definition of "system testing" I'm using: "Testing to assess the value of the system to people who matter." Those include stakeholders, application developers, end users, etc.

[Heston]

Exactly what I was thinking. Not to mention the prior experience with similar technologies.