Things I Was Wrong About: Types
I don&#x27;t really see most of my code being improved that much by types and I also see a lot of extra complexity that people in the sphere I am (indie games) have to deal with when using typed languages. It just doesn&#x27;t seem worth it. When you have to spend a lot of time fighting your language, and handling numerous extra concepts that don&#x27;t exist in an untyped language because they don&#x27;t need to, it feels like the people who swear by typed languages that they simply like creating extra work for themselves as a way to avoid doing what&#x27;s actually needed to be done, just because they want to feel productive.<p>I also suspect that a lot of this has to do with people&#x27;s personalities around the concept of borders. Some people like well defined borders in general in everything they do because they approach life from a more procedural perspective, and for procedures to work they need things to be in the right boxes and in the right places. While others prefer borders to be undefined and more free-flowing because more information can pass through concepts and that allows for a more unstructured design process. It only puzzles me that there&#x27;s so much energy in indie game development for highly bordered programming environments (i.e. all the energy being put into gamedev Rust libraries) when indie developers tend to be people who value borders less, as do all creative types. But I guess people really like types...