> After C# it's looks kinda naive. The biggest issue is that while technically > you can hide some parts of the library from user it's inconvenient. There is > no internal namespace scope where I can easily separate lib functionality > from the users code. Again, Nim is not C#, I understand that, but particulary > organization of code in C# feels easier. I spend a lot of time thinking how > to organize stuff in Nim ( heck, more time then actually writing the code XD > ) This is the biggest issue for me at the moment.
In my experience the different visibility levels that C# offers have an impact on one's productivity, always musing over which level to pick. I always ended up in a state where the C# compiler was happy but the result was pretty arbitrary. It didn't matter though, the costs of software development are in the bug hunting phase and visibility violations almost never produce bugs.
