I am currently in contact with an administrator who has to deploy a feature-solution from another dev.
The solution is deployed globally, which the admin does not like, cause it only is needed for one site collection. So he asked if the dev can change the scope.
His answer was, that this would be technically possible, but is deprecated, cause this would save the application in the IIS-bin of the web application. Deploying it globally instead would save the files inside the 15-hive (which is the one supported). That is why we should deploy globally and hide the feature in the wrong site collections.
Because I never heard of that (or find any clue online): Can someone validate this or in opposite state why this is wrong?
Be aware that I am NOT asking for opinions here, but for prove in form of urls etc.
(I am not in direct contact to the dev so I cannot ask him for more details)