Location project bin directory

I will have a look at it.

I'm not against source control tooling, I say I don't use it, because for me it is overkill. 

Thanks for a lot of tips, I'll pick and try them.

I started coding on Apple ][ back in the 80's. Mostly in machine language and for fun in basic. When Lisa and Mac where introduced I started coding in C. Only later I learned other languages from Fortran, Cobol, Pascal to RPG etc. I can't remember any source control systems in that time. I think IBM AS.400 had some kind of build in way of dealing with it, but my memory is not that great. Later except for C and C++ once in a while -and the environment I liked best Gain Momentum from Sybase- I mostly worked with script languages where the file system structure also for the team was the way of source control. The changes where always apart from the base source. Back then that was enough for the projects I worked on. I can see that working on more complex systems requires more than just a simple structure with some team rules ;).   I remember Virtual Sourcesafe but we didn't pick up on it back then because some complications I can't remember. I'm sure it al developed into way better tools now.

So for teams, sure I'd now choose to have source control aids. But since I'm alone I just want to have a trail of important changes without tool overhead. I can switch back to where I started discovering Monkey C from where I am now and al important steps are there (except for the development key I lost when I quit the Windows beta program).

My pain is in that I just can't understand some of the chooses for file locations that have been made by Garmin. Maybe it's because it's al becoming more virtual with those tools. I don't know. I just can't think of any reason why to mix data that needs to be in a source control situation with temporary files and reinstallables with a key that needs to be in backup. 

sublime? Are you crazy? That's too modern. I wouldn't even recommend vim. Just use plain old vi! :) 

I use git, and the 1st thing I do after I create a new Monkey C project is to copy the .gitignore and the .vscode/* to the new project. I think that the 2 things do different things, otherwise I wouldn't have both. But maybe it was changed recently and now you don't need the settings.json part I sent.

This is industry standard as for default destination. Both in maven (target/) and gradle (build/) and not to talk about make, by default the destination is thankfully inside the project's directory. Just think about how chaotic (or maybe unreliable) it would be if they all used /tmp/ for example