Remi Rousselet

The wording matters because the current usage paints the majority as evil. This makes people less likely to want to fix the problems If instead of saying "give up your power", we said "help others reach the same level", I'm sure more people would help.

I feel that "privilege" is misused a lot nowadays Take poor vs mid vs rich: Being mid-class is not a privilege. It's poverty that is a disadvantage, and the privileged are the rich The goal is not to make everyone poor, but to erase poverty and reduce the impact of being rich.

Of course, feel free to create issues and ask questions in case there is something you do not understand/feel is missing.

Multiple times complex scenarios popped into my mind, which made me panic thinking I found a case that forced me to re-think everything. But only to realize that, because of uni-directional flow, either it cannot happen or it's supported by default

If reinventing state-management from scratch these past few months have thought me anything, that is: Uni-directional data-flow is your best friend The possibilities it removes makes everything so much easier and allow what would be O(N^2) to be O(N)

Day - 1 before some cool announcement~ Say tuned for yet another state management solution, because we never have enough of them

Spams are getting smarter I've just received a mail saying nothing but "Hi Rémi, how are you?" Then, only after answering, do I receive the spam content. So it bypass Gmail's spam filter has I've already answered

Note: In case you are unaware of it, you can make your own `http://context.read ` if you are unsatisfied with that assertion: extension on BuildContext { T myRead<T>() => Provider.of<T>(this, listen: false); }

Writing maintainable code is all about removing possibilities. The fewer possibilities, the easier it is learn/test/change. That's why we avoid globals public mutable dynamic variables.

Writing documentation is so tiring It makes the documentation of Flutter/flutter_bloc/mobx even more impressive They all did such a good job

More generally, using `late` means that you will need "getters" far less often. You won't need to do the following anymore: Something _value; Something get value => _value ??= Something(...) And instead can do: late final value = Something(...)