@sherjilozair
That are very subjective recommendations, with some disadvantages.
"nim program" as a default alias for "nim c -r program.nim" with hidden
executable would mean that program is compiled again and again for each
execution -- until user discovers that he can just execute the binary. Maybe
indeed less surprising for people who only know scripting languages.
For nimcache -- I am using this to not stressing my SSD too much (with /tmp
mounted to ram):
cat nim.cfg
nimcache:"/tmp/$projectdir"
You are talking about "beginner programmers" \-- when you mean people with
absolutely no prior programming experience, then we have to think about if we
should recommend Nim at all for these people. I think Nim can be a good first
(and only) language for these people, maybe at high school or first university
course. But we know that it is not yet used there. And for self studies Nim may
be still a bit hard, as we have not large numbers of very good quality
documentation and large user communities in all mayor native languages. Also we
don't have libraries for all possible use cases beginners may be interested in,
and finally the compiler still has some minor bugs, which also is not that
optimal for beginners.
