Here is a little experiment. 1. Write a sample code, explicitly use style insensitive in the code 2. Show it to some colleagues who doesn't know nim 3. Try to explain to them the code without bringing style insensitive up unless they ask 4. They will definitely ask why you have get_data() and getData() 5. Explain to them how it doesn't matter 6. Take their opinion on that
You will not have a problem explaining the code to them since nim is so concise and expressive, and I'm sure they will love it. Now, colleagues read each other code all the time, so maybe instead of asking ourselves if we like style insensitivity, we should ask if those whom we work with would welcome it into our production pipeline, and wouldn't mind adopting nim in a team project. I'll keep using Nim, regardless of the result of this discussion, and I'm looking forward to replace Go completely with Nim (and/or Zig) in the future, but one of many things I appreciate in Go is code consistency, and how I can read code I wrote years ago, and still understand why I wrote it, and what each part means.
