I'm actually for doing the same as what was done with LocalizeString. The latter is a shortcut in the module base class to Localization.GetString(key, LocalResourceFile). And this will automatically back up to SharedResources of the module (and even DNN) if the string is not found. But I like the pattern of putting an oft used function into the base class to help with code clutter. So we could have LocalizeStringJS(key) or something similar (keeping the start of the string the same helps in the intellisense of course).