What are the tradeoffs of using a global service locator pattern like GetIt compared to using a more structured, compile time safe dependency injection framework such as the riverpod based provider system?

A global service locator like GetIt is generally quite simple to set up and use, but its dependencies are resolved at runtime rather than being verified at compile time, meaning a genuine mistake, such as forgetting to register a specific required dependency, is only actually discovered when that code path is genuinely executed rather than being caught immediately by the compiler, whereas a framework like Riverpod provides considerably more compile time safety and a clearer, more explicit way to express and verify the actual full dependency graph between different providers, at the cost of a somewhat steeper initial learning curve and generally requiring the provider to actually be accessed from within an appropriate widget context.

// GetIt: runtime resolution
final service = getIt<OrderService>();

// Riverpod: compile time verified provider
final orderServiceProvider = Provider((ref) => OrderService(ref.watch(apiClientProvider)));