Flock, a community driven Flutter fork.
My personal opinion on why it won't work, the right solution in the wrong solution space.

This will be a very long 🧵
#flutter #flutterdev

⬇️

https://twitter.com/SuprDeclarative/status/1850944417726939395

I assume you read all the reasoning @SuprDeclarative did about Flutter, the Flutter team, Flutter development, Flutter contribution, which lead him upon the decision to fork Flutter and create Flock.
I respect him, and agree with lots of his reasoning, so I should be fairly
⬇️

As you asked, @RydMike . I try to be short, I really try 😅

"I messed up with riverpod ChangeNotifierProvider and StateNotifierProvider concepts both work with mutability and immutability respectively"

This is a misconception, and it's not true

1/n

https://twitter.com/RydMike/status/1616075591186513920

There's this dualism in riverpod's docs:

ChangeNotifier/Provider <-> mutable state
StateNotifier/Provider <-> immutable state

But is it really so?
Spoiler: is not.

2/n

So yesterday I read this article. There were comments from @RydMike and @gaetschwartz that I really respect, but I find at least misleading. The article itself is very controversial, but mainly wrong. So I guess is time to bisect, and give my own personal opinions

A thread 👇👇

https://twitter.com/AMiiite/status/1373914010643468290

First of all, the article. It's wrong from many povs, but the part I like the less, is that it juxtaposes Dart and kotlin. Those are just two languages, not to rival cities fighting for access to the water. I hear often "Why Dart is not kotlin", and I'll address it in the end 1/n