Globals vs. classes to store theme config

I am trying to get a feel for what are the best practices when needed to have reusable variables across theme files. Right now I a settings.php file that is being included within functions.php. In this file I would like to assign variables for global settings such as directory paths, module names, etc.

Here is a very basic rundown of what I would do if I were to use globals:

/**
 * Directories
 */
$GLOBALS['theme-dir']	     = get_stylesheet_directory_uri();
$GLOBALS['styles-dir']	     = $GLOBALS['theme-dir'] . '/dist/styles';
$GLOBALS['scripts-dir']	     = $GLOBALS['theme-dir'] . '/dist/scripts';
$GLOBALS['fonts-dir']	     = $GLOBALS['theme-dir'] . '/dist/fonts';
$GLOBALS['fc-layouts-dir']   = 'templates/fc-layouts';

/**
 * Layouts
 */
$layouts = [
	'blue-highlights',
	'carousel',
	'centered-content',
	'custom',
	'hero',
	'list-items',
	'product-highlights'
];

$GLOBALS['fc-layouts'] = array();

if( $layouts ) {
	foreach( $layouts as $layout ) {
		$GLOBALS['fc-layouts'][] = $layout;
	}
}

Now to be safe I would probably need to “namespace” the global variable names, but I’m assuming that this is not the best way to do this and I know usually people want to stay away from using globals like this. Is there a cleaner way to achieve similar results using classes?