Why doesn't BlocSignal need Provider like classic BLoC did?
Dropping package:provider ends dependency hell, fixes Flutter's ghost rebuild bug, and brings zero-code-gen reactivity:
Randal Schwartz🥇 💙
@RandalSchwartz
Google Developer Expert in Dart/Flutter.
Five decade industry veteran.
(The artist formerly known as @merlyn)
- Working on some art for my upcoming BlocSignal presentations. Of course, they all have a rail theme, since that's the secret background story for the name of the package.
- Ever had an error SnackBar re-trigger on phone rotation? Sticky domain state is the culprit. Here is why classic BLoC needed bloc_presentation, and how BlocSignal solves one-shot UI side effects with zero dependencies:
- 100K ops/sec reactive web app in pure Dart ⚡ Dogfooding bloc_signals_jaspr on blocsignal.dev: • 0ms microtask latency in JS • Full router built as a Cubit • Scoped updates with Selectors • Clean Dart 3.13 syntax dev.to/gde/dogfooding…
- Dart 3.13 + BlocSignal = Zero Boilerplate! 🚀 Primary constructors, 'this' bodies, and shorthands make Flutter state management concise & 0ms synchronous: dev.to/gde/dart-313-p… #Flutter #Dart #BlocSignal
