Just typical zealotry. So instead of globals we should use DependencyInjection, and now the app is magically better? For many projects it hardly matters, and I'm not going to over complicate things when there's no practical reason for it.
Is making them properties and sticking them in a "GlobalVariablesByAnotherName" singleton and chucking that around better? Possibly. Possibly not.
I have found, however, that any code where someone has used global variables is hard to share with other developers. Maybe that's the crux of the matter.
Used to be you wouldn't use globals because it was difficult to figure out what code accessed or changed their values. Now that's a right click away.