> If you structure your project with virtual folders, why couldn't it be the same structure on disk !!!!
The primary reason is because files moving on disk complicates source code control considerably. During development, I may move a given VI between virtual folders all the time -- especially if I'm using access scope on the folder or if my library is big enough to warrant palette hierarchy. That can often break source code control tracking of changes. Some SCC providers are better than others in this regard, but all of them have some amount of complexity.
The goal of the project was to divorce these as far apart as possible and to stop worrying about the disk layout until you were done with your project's development and ready to create a distribution. We've observed many users and seen that most are more successful the less they worry about the disk configuration and instead concentrate on their VI layouts.
...