Комментарии:
I can t believe this nonesense. And flutter devs think they re smart ...
ОтветитьNo sabia que un tutorial podia iniciar con el final y terminar con el inicio, para alguien que inicia en Flutter esto es catastrofico. Porque pre-asumimos que dichas Clases Task and TaskNotifier podrian ser nombres reservados.
ОтветитьIn Flutter the Best Package for Managing State Management is Getx
Ответитьanyone has the link for the last part of this intro to flutter series? cant seem to find it anywhere
ОтветитьWhy does the code rebuild the list of checkboxs for just one user check action? If I added thousand of items throughout my life, it is going to be slow when I check.
ОтветитьGreat! thank you.
Ответить"Let's pick up where we left last time"
I see what you did there
flutter translate vietnamese very few
Ответитьand the what's function of setState? kasih tau dong yg tau :(
apakah harus menggunakan state management untuk handle errorMessage
Where is the source code of this task project?
ОтветитьGreat solution for state management =)
ОтветитьGetBuilder state managment???? Is the better. Please talk about
Ответитьcame from scopedModel. then provider. then to inheritedWidget. with streamControllers. basically provider of my own
ОтветитьWhat is next video?
ОтветитьI NEED HELP!
hi guys, i'm beginner on flutter development and i am just trying to implement what we are learning on this video ( flutter state management using flutter_riverpod), but i got an error in my StateNotifierProvider. could anyone help me ?
obs: I'm learning english too, sorry for any mistake i've made. kkk
Riverpod 🤩
ОтветитьThanks for this video, Khanh! Extremely gnarly topic, well explained. And it's clear you took great care in striking the balance between giving people useful advice, and starting a flame war. Cheers!
P.S.: Seeing the provider and consumer blobs put a big smile on my face!
Nice video. At this time I still prefer to use Bloc mainly because it works so well in teams.
It's more opinionated than Riverpod which (I guess) makes it less flexible but when working in teams or in situations where another developer is going to have to look at my code half a year from now it's really nice because it forces the developers to write code in a certain way, which creates consistency. That consistency is important so that the developers can understand each other's code better without running into surprises.
does not explain how _TaskItemState extends State<TaskItem> needs to be changed to support WidgetRef paramenter in build. This is where learning something becomes frustrating and all the hard work and easy explanations become an insult to someone who just wants to learn. the out of sequence presentation of changes makes it much worse. if you are showcasing your framework, please dont label it as a tutorial.
ОтветитьI would love to have a course like Google Garage about Flutter 🙏🏻
ОтветитьGot a big smile on my face when i saw that you are "promoting" riverpod on this official channel. Best state management solution for flutter for sure!
ОтветитьI was having two options: React or Flutter. And I am glad I chose Flutter. This is one of the most amazing and energetic community of developers. No doubt Flutter will touch skies in the coming years.
ОтветитьPlease make a flutter splash screen animation tutorial. 😊
ОтветитьPlease teach us from Start like beginner please make
ОтветитьThis is an awesome explanation! Very easy to understand. Althought if you have team with mixed expertise. Then using riverpod can quickly get messy and then you have to reinvent the concepts of how to structure your code. In bloc, the standards are well defined. You have 3 files - State, Events and the bloc. Anyone starts new does have to feel like they are lost in the woods when looking at the code.
ОтветитьHi y'all! I just wanted to say thank you for keeping the dialogue going on this video and keeping things respectful! I know state management can be a contentious topic where we can have strong, varying opinions. Naturally, I was a bit hesitant taking on this video 🫣 but seeing the responses and conversations on your preferred state management tell me that the effort has paid off :) Thank you for being an awesome community with such a welcoming environment!
ОтветитьNeed more like this to learn flutter
ОтветитьI understand Google recommends Provider.. but with so many state management tools and approaches, it would be nice to have guidelines for best practices.
Ответить👍👍
ОтветитьI'm using BLoC and it's scalable and easy to use. I suggest to check its toturials because you learn how to develop application using feature driven architecture
ОтветитьJust use kmm with compose...
Ответитьriverpod is rock solid! we use it in prod for over a year already 🤞
Now only thing that I wish for is static metaprogramming, since it'd makes riverpod even more intuitive to use.
Riverpod is best State management Solutions
Ответитьintroducing tauri 🗿
ОтветитьYou are great. I have been working with state management solutions for a long time understanding little of it. This video makes understanding those solutions pretty easy and I am thankful for that. Keep up those videos! :D
ОтветитьFlutter's UI code, out-of-box support and documentation are awesome. Plus I love coding in dart. Still can't use in webdev cause after build its heavy and slow, specially lag in animation. Really hope it gets better and better. Although mobile and desktop builds seem fine.
ОтветитьLove Blocs and Riverpod, but still use Redux + Epics combo in production :D
ОтветитьWhat's the title of video from previous?
ОтветитьFor me, Riverpod is a breath of fresh air. I came from Provider, and it will become a mess quickly. I find it a little more exhaustive on debugging than Riverpod.
Also, I like the concept of AsyncValue in Riverpod.
Riverpod is definitely the best state management library available for flutter
ОтветитьNice concise video. But my goto choice is still cubits. Perfect for bigger apps. You can have full control. And UI is more separated from business logic.
ОтветитьJust started riverpod and it has been awesome!!
ОтветитьAwesome!
ОтветитьUp
ОтветитьNice!
ОтветитьScoped model, provider, inherited widgets are usually my go to choices
Ответитьriverpod to me is the worse choose for many reasons, we loose encapsulation and a lot of OOP concepts. The best solution I can suggest for maintainable project is to make providers as privet other ways you don't know in which place you change the state.
ОтветитьRiverpod is fantastic, great video
ОтветитьGood keep going.
Ответить