This video is amazing. What I really appreciate is your ability to articulate WHY we would use this pattern. As a beginning computer programmer, this is helping me properly contextualize the content to make it more "sticky" in my head. Thank you so much for sharing your knowledge with the world!
When I was in your shoes I had the same struggles :) and while making the videos I try to answer: "I wish someone explained to me this and that at the time...". Am so glad the videos are helping you! Cheers!
Great tutorial! I don't think we'll need this pattern as much compared to other structural design patterns like Facade or Bridge. However, the strategy behind this pattern is quite important.
I don't know if its intentional or not, but the style of these videos is similar to the Portal 2 aperture science instructional parts (even the voice resembles the voice acting in Portal Stories: Mel). Regardless, I LOVE this style! Thank you.
This one was good. Thanks for helping me out !! Also explaining on slides with code example helps understand betterr (which this one was) rather typing in real time and swithching multiple screen.
Hey ! Great explanations, thanks ! In the bookfactory, why do you only compare the type and not all the intrinsic values? If I understand correctly, there will be only once the type "action" and once the type "Fantasy" without caring about the different distributors and otherdatas. Thanks for your answer.
A better name for it would be BookTypeFactory I guess! Sorry for the confusion :) And we are doing that because the attributes stored inside the Type are what is being repeated between books, the others may vary. Hope this helps!
Nice and very clear! Just one question... does the flyweight pattern contemplate any particular sort of data structure when storing already created flyweights, something like a recursive tree?
Happy to be of help! It depends on your use-case, however, Maps are the most popular because of the ability to retrieve an object in constant time by value :)
I thought I understood from the video but when I saw your implementation code in github it doesn't match to the class diagram in video. This leads to more confusion. For example there is no 'Store' class in video and in 'Book' and 'BookType' class there are no methods as shown in video, could you please explain? Also, 'BookType' which is in 'BookFactory' class but not imported, not sure how the code even compiled in the first place? Though appreciate your efforts to explain the concept easily! Thanks.
Glad I could help! - There is a store class in the GitHub repo plz have another look... - There are no methods in the Book and BookType classes in the video as well... - No need to import it because they are in the same package... Cheers!
@@geekific Thanks for the response. Let me frame questions well: - What does the 'Store' class represents in classdiagram? - Aren't the 'context' and 'operation' the methods in Book and BookType classes as shown in classdiagram?
No. For sure, "cashue" would be pronounced more like ['kæʃju] but he actually said [ka'ʃeː]. If you want a transliteration in cursed English spelling, then I would rather suggest "caché", as in "cliché". (Yes, I believe making it look like a French loanword is actually the best option here.)
Dude in 7mins you are delivering more value than that delivered in a 3-hour lecture...! Thx
Thank you! This means a lot :)
@@geekific funny enough my OOP class in uni pretty much copied this playlist word by word for any explenation about design patterns
This video is amazing. What I really appreciate is your ability to articulate WHY we would use this pattern. As a beginning computer programmer, this is helping me properly contextualize the content to make it more "sticky" in my head. Thank you so much for sharing your knowledge with the world!
When I was in your shoes I had the same struggles :) and while making the videos I try to answer: "I wish someone explained to me this and that at the time...". Am so glad the videos are helping you! Cheers!
Very nice and clear video for me. Thank you very much, sir! I can now understand this pattern in 7mins
This is a very good explanation of flyweight. Thumbs up
Great tutorial! I don't think we'll need this pattern as much compared to other structural design patterns like Facade or Bridge. However, the strategy behind this pattern is quite important.
Glad it helped! It sure is :)
Hi, this is the best flyweight explanation i could find on youtube (the other ones were horrible to be honest).
Glad it was helpful!
This was very easy to understand, thank you!!!
😁
I'm so glad it was :)
UNISA COS2614 students should be watching these videos. Very useful man
Great content. You deserve more followers
I appreciate that! Glad you liked it :)
I don't know if its intentional or not, but the style of these videos is similar to the Portal 2 aperture science instructional parts (even the voice resembles the voice acting in Portal Stories: Mel).
Regardless, I LOVE this style! Thank you.
This one was good. Thanks for helping me out !!
Also explaining on slides with code example helps understand betterr (which this one was) rather typing in real time and swithching multiple screen.
Thank you! Happy it helped :)
Hey ! Great explanations, thanks !
In the bookfactory, why do you only compare the type and not all the intrinsic values? If I understand correctly, there will be only once the type "action" and once the type "Fantasy" without caring about the different distributors and otherdatas.
Thanks for your answer.
A better name for it would be BookTypeFactory I guess! Sorry for the confusion :) And we are doing that because the attributes stored inside the Type are what is being repeated between books, the others may vary. Hope this helps!
@@geekific Thank you for your answer and especially the quality of your video !
Nice and very clear! Just one question... does the flyweight pattern contemplate any particular sort of data structure when storing already created flyweights, something like a recursive tree?
Happy to be of help! It depends on your use-case, however, Maps are the most popular because of the ability to retrieve an object in constant time by value :)
God bless you!
please do a video about the livingrimoire AGI software design pattern
I thought I understood from the video but when I saw your implementation code in github it doesn't match to the class diagram in video. This leads to more confusion. For example there is no 'Store' class in video and in 'Book' and 'BookType' class there are no methods as shown in video, could you please explain? Also, 'BookType' which is in 'BookFactory' class but not imported, not sure how the code even compiled in the first place?
Though appreciate your efforts to explain the concept easily! Thanks.
Glad I could help!
- There is a store class in the GitHub repo plz have another look...
- There are no methods in the Book and BookType classes in the video as well...
- No need to import it because they are in the same package...
Cheers!
@@geekific Thanks for the response. Let me frame questions well:
- What does the 'Store' class represents in classdiagram?
- Aren't the 'context' and 'operation' the methods in Book and BookType classes as shown in classdiagram?
Perfect
did i just hear cache being pronounced cashue? 3:53
yes
No. For sure, "cashue" would be pronounced more like ['kæʃju] but he actually said [ka'ʃeː]. If you want a transliteration in cursed English spelling, then I would rather suggest "caché", as in "cliché". (Yes, I believe making it look like a French loanword is actually the best option here.)
Cashé
Thanks! Although, Java is one of the worst languages, especially for explaining computer science concepts.
Glad I could help! Java is very verbose, that is why I actually find it easier to teach stuff with it!