|
Historically, scientific progress has extremely rarely been made by companies. Most of the time, it's the result of academic research. Most researchers typically have neither time nor inclination to build a company/a product based on their own research, and having great research is no guarantee that the company/product will succeed. So the way research results become visible is typically through publications and teaching. When companies hire graduates who have learnt from researchers, some of these graduates end up in position to "innovate", quite a few years after the actual research has been done. For instance, I'm going to talk about the field that I know best: programming languages (to keep it simple, I'm not talking of VMs or compilers, just the languages). Pretty much everything you see in Java, C#, Python or Go dates back to the 70s (with broader testing and quality of life improvements, of course), Swift gets a few improvements imported from the 80s, but not that many. The only industrial languages that seem to have real innovations are F#, Rust and Scala, which are three cases in which the actual researchers managed to convince (or found) a company to support the language. Anyway, it's really, really hard to measure scientific progress, and if you look at companies to try and gauge it, you're looking at stuff that is typically quite old. |
I would also note: in spite of "novelty" requirements for publication, we tend to see many of the same ideas recycled over and over. Which makes sense, because they tend to be good and useful ideas that may be fundamental to the discipline.