# Unstructured data **URL:** https://fortran-lang.discourse.group/t/unstructured-data/2811 **Category:** Uncategorized **Created:** [February 17, 2022, 6:09pm UTC](https://fortran-lang.discourse.group/t/unstructured-data/2811 "2022-02-17T18:09:55Z") **Posts on this page:** 1 **Showing post:** 23
### Author: ![shahmoradi](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/shahmoradi/32/3151_2.png) [@shahmoradi](https://fortran-lang.discourse.group/u/shahmoradi) #### Post date: [February 20, 2022, 11:42pm UTC](https://fortran-lang.discourse.group/t/unstructured-data/2811/23 "2022-02-20T23:42:22Z")
Other languages with such features have to write endless pages of guidance and warnings for people to avoid such patterns (See [here](https://docs.julialang.org/en/v1/manual/performance-tips/#man-performance-abstract-container) and [here](https://johnysswlab.com/the-price-of-dynamic-memory-allocation/) for examples). Fortran appears to prevent it altogether if the potential damages outweigh the benefits. And that’s what makes Fortran fast, with no hassles and no warnings manual. Over the years, I have seen many (frequently unfair and unjustified) criticisms of the Fortran language. Still, almost every time I dug into the issues further, I realized the standard committee had excellent reasons to design things the way they are. That does not mean everything is perfect. In particular, the patchy and selective style of enhancements to the language, which FortranFan also [mentioned earlier](https://fortran-lang.discourse.group/t/glmnet-migrates-to-c/2225/13), is, has been, and will remain quite detrimental to the language. That’s my opinion as a frequent user, from the user perspective. --- _[View the full topic](https://fortran-lang.discourse.group/t/unstructured-data/2811)._