# Resistance to modernization

**URL:** <https://fortran-lang.discourse.group/t/resistance-to-modernization/4136>\
**Category:** Uncategorized\
**Created:** [August 8, 2022, 8:23pm UTC](https://fortran-lang.discourse.group/t/resistance-to-modernization/4136 "2022-08-08T20:23:21Z")\
**Posts on this page:** 1\
**Showing post:** 98

<div class="post-metadata">

**Author:** ![RonShepard](https://avatars.discourse-cdn.com/v4/letter/r/a3d4f5/32.png) [@RonShepard](https://fortran-lang.discourse.group/u/RonShepard)\
**Post date:** [August 18, 2022, 9:07pm UTC](https://fortran-lang.discourse.group/t/resistance-to-modernization/4136/98 "2022-08-18T21:07:29Z")

</div>

I was thinking about this thread [Does LAPACK/BLAS automatically use multi cores or threads?](https://fortran-lang.discourse.group/t/does-lapack-blas-automatically-use-multi-cores-or-threads/4072), but they both covered some of the same ground.

Yes, synthetic benchmarks can be unrealistic. I’ve seen compilers remove entire do loops in benchmarks because they recognize and remove dead code. But in general I’ve found that what one learns with tuning and optimizing benchmarks can be applied also to optimizing production codes.

---

_[View the full topic](https://fortran-lang.discourse.group/t/resistance-to-modernization/4136)._