No video

Making React Context FAST!

  Рет қаралды 87,653

Jack Herrington

Jack Herrington

Күн бұрын

Пікірлер: 436
@norberthorgas2428
@norberthorgas2428 Жыл бұрын
I have been working with React for about 4 years and recently started teaching React to juniors. Today I feel like I am a junior again 😀 Thanks for sharing this amazing content Jack!!
@ljuglampa
@ljuglampa Жыл бұрын
I've made this "fast context" solution a few times. The thing is, you don't even need any Provider here. You can just use any external object with the same pub/sub api, since we're triggering re-renders manually, so this useStore hook can pick its store from wherever, not just from a context. Also, when you do useRef(new Set(...) you're re-creating this Set for every render of that custom hook. It won't care about the value but still, it's "cleaner" to do: if (!store.current) store.current = new Set(...) to make it just happen once. Otherwise awesome content Jack. I love the useSyncExternalStore abstraction to get rid of setting up local states manually. Feels safer also to have React internals take care of that part.
@untitleddocument4197
@untitleddocument4197 Жыл бұрын
Good point :D I guess this also means you could use a store that syncs with localstorage, if it made sense too
@PeerReynders
@PeerReynders Жыл бұрын
The Provider and the `useStore()` hook are fine. They decouple the components from the source which is useful for developer tests and for inclusion in design system guides. However, especially as `useSyncExternalStore` is being used, there is no need for `useStoreData()` to be a hook so it can just be implemented as a vanilla `createStore` function without all the `useRef()`and `useCallback()` complexity. Also since the properties in the created { set, get, subscribe } object are stable through the lifetime of the application it makes sense to just bind it to a `store` variable within the closure created by `createFastContext()` that both `createContext` and `StoreContext.Provider value` can use to eliminate the initial `null`.
@asdfasdfuhf
@asdfasdfuhf Ай бұрын
@@PeerReynders "so it can just be implemented as a vanilla createStore function without all the useRef and useCallback complexity" -- are you suggesting to just use `let var = ...` variables instead of useRef? I.e. rewrite createStore to be pure javascript, no react?
@alexlohr7366
@alexlohr7366 Жыл бұрын
Small remark: if you are storing your data in a ref in any case, there is no need to overwrite it with a new object that destructures both the current data and the updates, instead use Object.assign to copy over the partial values for a little better performance. Otherwise, this is a nice pattern and you've done a great job showing how it comes together, @Jack Herrington!
@talatkuyuk6556
@talatkuyuk6556 Жыл бұрын
How ? [line-22] if I use Object assign ------> store.current = Object.assign(store.current, value); but TypeScript says (Type 'Partial' is not assignable to type 'Store')
@alexlohr7366
@alexlohr7366 Жыл бұрын
@@talatkuyuk6556 in this case, you can cast value to store. This is a shortcoming of TypeScript.
@talatkuyuk6556
@talatkuyuk6556 Жыл бұрын
@@alexlohr7366 Nope, I casted the value as Store; but Object.assign first parameter should extend {} in nature; TypeScript is still angry.
@mortezatourani7772
@mortezatourani7772 Жыл бұрын
@@talatkuyuk6556 What about this: `Object.assign(store.current, value);`
@PeerReynders
@PeerReynders Жыл бұрын
@@talatkuyuk6556 You have to constrain Store's type-note below the `Store extends Record`: export default function createFastContext(initialState: Store) { … const set = useCallback((value: Partial) => { Object.assign(store.current, value); subscribers.current.forEach((callback) => callback()); }, []);
@nikolagospodinov9057
@nikolagospodinov9057 Жыл бұрын
Jack, thank you for all your videos! Thanks to you I leveled up my skills and got to a senior position! I hope you come out with a course soon describing all of the mid/advanced React concepts, best practices, project structuring, when and how to use 3rd party libraries like RQ, state management, and all those good stuff. I would literally pay anything for that!
@jherr
@jherr Жыл бұрын
'Anything'? I can imagine? kzfaq.info/get/bejne/qMBye8yl2J6ugH0.html
@quelchx
@quelchx Жыл бұрын
React Query as some excellent documentation -- dedicate a day to browse through it and you will be surprised what you will be able to accomplish with that library. My companies application has some complicated state between the server and client and react query has made it so easy to manage state, handle mutations + hydrating the client. It only took me a few days of going through the documentation and now I feel fluent with talking to that library -- it shouldn't take you very long if you dedicate a few hours to it.
@jherr
@jherr Жыл бұрын
@@quelchx kzfaq.info/get/bejne/gMd9ZdV23dPRoac.html
@quelchx
@quelchx Жыл бұрын
@@jherr I have watched this video =). When I first used RQ I thought it was more for data fetching and managing it's state but I have used it to simply manage state from one component to another and mutate that state. I love RQ it's such a useful tool. Honestly Jack I have learned a lot through your content and have taken patterns you have provided and I use them daily =).
@jherr
@jherr Жыл бұрын
@@quelchx Thank you so much!
@mortezatourani7772
@mortezatourani7772 Жыл бұрын
Let's make react context great again :) I think the actual implementation of context should be something like this and the current version is really deficient. And again really enjoyed the way you went step by step, improved the solution, and made it generic. It not only helps with understanding the process but also demonstrates how to eat an elephant. Thanks again.
@monastyrskiiden
@monastyrskiiden Жыл бұрын
What a wonderful explanation, I've been working with React for over 4 years already, and still, there's something new I get to discover every day.
@nathanfranck5822
@nathanfranck5822 Жыл бұрын
Jack writing a solid library in real-time is just incredible. Love to see it and super empowering for anyone looking in to see that you don't need 100 npm packages in your project to make something super solid and robust! The more code that you can own and understand yourself now means more flexibility and creativity later as you figure out what your project is and can be. Also helps even if you're using pre-built libraries to explore in code yourself to know exactly what you want out of a library and cut through all the bullshit you don't need.
@scottsmith416
@scottsmith416 10 ай бұрын
I've been looking for a solution like this for years! Thanks, Jack!
@igogs7095
@igogs7095 Жыл бұрын
Such a great lesson! This channel is diamond for ones who wanna become really good at react! Awesome job, thank you!
@DEVDerr
@DEVDerr Жыл бұрын
You have almost introduced fine-grained reactivity to React like it is for Solid and Svelte. Fantastic job 🔥 Wondering why React did not yet implement such a thing lol
@creatorsremose
@creatorsremose Жыл бұрын
Jack, it's like you're following my work and post videos that are surgically relevant to my challenges. You're so awesome. Thank you so much.
@quelchx
@quelchx Жыл бұрын
Using React Context and patterns like what you have shown too me is more than enough for a bunch of use cases. I'm glad to see a video like this so I can point some of our developers we hire to this video to get a gist of what I call baked into React for global state management using HOC patterns. Im sure I'm not alone with feeling like this but once you learn a few state management patterns/libraries (Zustand, Jotai, React Query, Redux, React Context patterns) I enjoy using almost all of them and when it comes to making a choice on which one to use I often struggle to make a choice because they are all great IMO (for React apps) Thanks again for all the content you provide to the React Ecosystem it's great, absolutely love the content -- your a great guy for all the work you provide towards developers coming into this gig.
@josephizang6187
@josephizang6187 Жыл бұрын
Thank you Jack, the time you take to make your content..with so much thought and care makes every video a gem. Again, thank you.
@Chrosam
@Chrosam Жыл бұрын
I haven't seen the video yet, but based on previous videos I know it's gonna be amazing. I like that you don't only show HOW to do it, but WHY you do it. Here, you dropped this, king 👑
@Chrosam
@Chrosam Жыл бұрын
Done, yep, as expected, never fails to amaze.
@ynonshoshan
@ynonshoshan Жыл бұрын
in my eyes this should be an essential upgrade to react and should be an available hook that comes right out of the box, thanks for this!
@loia5tqd001
@loia5tqd001 Жыл бұрын
I'm really interested in seeing how this would get involved in a more complex application, please do so Jack. For example: - involving async actions - actions that need states from different stores or fields of store
@wonjunjang3839
@wonjunjang3839 Жыл бұрын
This is so high-quality as a junior frontend dev your contents are really helping me write neat-codes,
@matt35953
@matt35953 Жыл бұрын
Jack, you a a legend! Spent most of yesterday looking at state mangers to address this kind of issue... glad I took a "KZfaq break."
@bushigi5913
@bushigi5913 Жыл бұрын
What kind of solution is this!! You just made my understanding of react to another level! Thank you so much, I'll definitely come back to watch this video again and again.
@igrb
@igrb Жыл бұрын
This was so instructive, I love how you teach not only these cool patterns but the reasoning behind them AND colol little details like the Partial there. Thanks Jack!
@zachatack21
@zachatack21 5 ай бұрын
This is an absolutely incredible tutorial! I learned a ton from this! I understand context, useRefs, and how components rerender SO much better now! Thank you!!!
@lilpodbebe
@lilpodbebe Жыл бұрын
Brilliant! I need this to maintain a complex form without a complete rewrite. Thank you! 🤩
@cristiang4774
@cristiang4774 Жыл бұрын
This tutorial blew my mind (in a positive way). Amazing stuff!
@JhonLavigne
@JhonLavigne Жыл бұрын
Jack, this is by far the most interesting video about state management in React that I have ever seen. Holy shit, Sir. you are a Beast.
@shivamjhaa
@shivamjhaa Жыл бұрын
At this point, I don't really know how you keep coming up with a new cooler video. Thanks, from India
@MajdBaddour
@MajdBaddour Жыл бұрын
A superb solution, refactored to perfection. That was an excellent video, as always. Thank you Jack for all you do.
@marouaniAymen
@marouaniAymen Жыл бұрын
In my experience, I use React context when it is limited in a very narrow part of the components tree, when the state to share is not internal and will wrap a big part of my application, I use Redux Toolkit, I found it very awesome. For server state management, react-query for sure.
@Rico-cp4xp
@Rico-cp4xp Жыл бұрын
I can't tell you how much I appreciate your videos Jack. You're a great teacher! 🙏
@Nonsense116
@Nonsense116 Жыл бұрын
I was able to predict what direction you were going to go as you went along. When I first started watching your channel a lot of what you talked about sounded like voodoo magic. The only reason I was able to predict before hand what you would do is because people like you are incredibly skilled and offer up high quality educational content. I often reference or recommend this channel to my coworkers. I really can't thank you enough and I still learned something new as I normally do with your videos. Thank you for being a part of keeping my skills fresh and staying highly motivated to stay curious.
@sissipwns
@sissipwns Жыл бұрын
Omg just realizing that context is initially designed for slow-changing-stuff really enhanced my mental model of React. Thanks so much for your videos, you are the coding buddy I don't have :)
@axe-z8316
@axe-z8316 Жыл бұрын
Hey long time interested, but now full fledged fan, this is hands down your best stuff to date. Amazing
@clouatre3034
@clouatre3034 Жыл бұрын
It's incredible how much I have learned from you. Thank you once again!
@AlJey007
@AlJey007 Жыл бұрын
I was playing around with your code and came to a realization that the magic is entirely in the useSyncExternalStore method and the context is 100% superfluous, it is not doing anything at all. In fact, useRef and useCallback are also redundant. With a few tiny tweaks this useful code became a game changer for me. Thank you for this video!
@frostmichael8360
@frostmichael8360 Жыл бұрын
It's a rainy and windy sunday, i drink a cup of tea and i'm definitly fallen in love with your code and conception. Thank you !
@parsanasirimehr7267
@parsanasirimehr7267 Жыл бұрын
I love it when these type of ideas come along. I wouldn't use it for state management, but it has a lot of potential when it comes to Multilayer contexts that I deal with at work. It piles up little by little. Thanks Jack
@zlackbiro
@zlackbiro Жыл бұрын
This is the most insane video you made. This should be on npm as a library. 😁
@DIN_A8
@DIN_A8 Жыл бұрын
I never get tired of the view, what a zen-place to work from
@ynonshoshan
@ynonshoshan Жыл бұрын
That was bloody amazing
@mrasoahaingo
@mrasoahaingo Жыл бұрын
I really love the way you explain concept by doing step by step. It reminds me of Dan Abramov trying to re implement Redux from scratch. It make things clearer and straightforward. Really really enjoy your video format! Thanks!
@KPOPYakuzaz
@KPOPYakuzaz Жыл бұрын
Great content as usual, it's really hard to find react content at this level so it's highly appreciated. Great pattern, love the use of refs for this
@mikeks81
@mikeks81 Жыл бұрын
Really slick! Adopting this pattern immediately. Thanks for sharing!
@mysandyballs
@mysandyballs Жыл бұрын
Exactly what I was looking for to take context to the next level. Great work as always Jack 👍
@riman8493
@riman8493 Жыл бұрын
This was quite amazing and answers a pretty real need I actually have right now. Thank you _so much_ for putting this out there!
@talatkuyuk6556
@talatkuyuk6556 Жыл бұрын
Your solution is awesome; you are great guy to explain this kind of structural videos, thanks again.
@marlonmarcello
@marlonmarcello Жыл бұрын
Love your content Jack, thanks for this great explanation! I am a React dev, I work with it every day, and this kinda of hassle that we have to go through to get this level of performance is one of my biggest pet peeves with the framework. For my freelance projects I use Svelte and I get all of that for free, it's glorious. Looking forward to a video on the new upcoming SvelteKit!
@1235niki
@1235niki Жыл бұрын
Thanks for sharing this new pattern Jack. Really helpful.
@vakhtangnodadze4802
@vakhtangnodadze4802 Жыл бұрын
Awesome video Jack. Your videos are like goldmines.
@OleksandrDanylchenko2k
@OleksandrDanylchenko2k Жыл бұрын
Thanks 🙏 It's the clearest tutorial on how to implement the fast context
@BHFJohnny
@BHFJohnny Жыл бұрын
I once faced this challenge: 1) I fetched data from API 2) Based on that data, I should have rendered a slider for each item from a list. I didn't know the count on build time, I only knew it on run time 3) Based on current values of all the sliders, I should have calculated sum and some validation boolean (like isOverLimit or something) My initial naive way was to pass down value and onChange props from a container component. As expected, didn't go well at all. Slider can easily fire 1000 change events per second. All sliders needed to rerender. I was laggy and terrible UX. Second approach was to hack it with throttle. Each slider would have its own local state and once in a while (let's say once per 250ms), onChange was fired and calculation synced. Worked better, but it still needed to rerender all sliders, though not that often. Hacky, ugly, not nice. I did a quick research and and found Recoil. I implemented runtime atomic state for each slider, two selectors for calculated value, everything worked perfectly, only things that really changed had to be rerendered. Tried with 1000 sliders just out of curiosity, worked flawlessly, slide back and forth on 4K display, no lags, blazing fast. This solution looks good in a way that it could replace my solution entirely, without Recoil needed to be installed at all. Really nice. I like this ref - subscriber - selector approach. It's clean, neat and elegant. No hacks needed.
@somewonderfulguy
@somewonderfulguy 5 ай бұрын
I really love this combo. I'm going to use fast context in UI kit I develop (for fun and practice) as I see it reasonable to use React context instead of any 3rd party state management. Less dependencies better for UI kit. I made one modification, inside Provider component there are two providers now - one provides 'set', the other 'get' and 'subscribe'. And instead of useStore there are useStoreValue and useStoreDispatch now. There are cases when you have store setter that does not care about value, so component that uses setStore will never re-render as 'set' is always stable. Thanks for the video and solution it is awesome!
@hugot8226
@hugot8226 Жыл бұрын
That's SO VALUABLE Jack ! I was looking for a solution for exactly this problem for months. What an elegant solution !
@alanrice9935
@alanrice9935 Жыл бұрын
Great explanation, I've been toying around with using this context pattern and you explained some parts that I couldn't figure out
@BlurryBit
@BlurryBit Жыл бұрын
Lovely video! Concise, and very helpful!! Thank you Jack :)
@robwatson826
@robwatson826 Жыл бұрын
That pub/sub solution is great! I'm relatively new to React and hadn't considered that as a way to manage state "globally" and only re-render components that need to. Thanks for sharing this Jack
@tusharrai3644
@tusharrai3644 Жыл бұрын
Very sturdy implementation, just loved the approach and the way you explained. can't wait to Implement this fast context.
@corndoggydogdog
@corndoggydogdog Жыл бұрын
This is smashing, thank you so much Jack! 🔥🔥🔥🔥
@ozgursar5386
@ozgursar5386 Жыл бұрын
This tutorial is simply amazing. Thank you!
@SergeyChebykin
@SergeyChebykin Жыл бұрын
Jack, thanks a lot for making really excellent educational videos! This one is especially important, given how easy it is to misuse React context and end up being deep under a lot of performance issues. Thank you!
@ivanabadzhiev1214
@ivanabadzhiev1214 Жыл бұрын
Amazing, thank you Jack for all the value you provide with your videos
@b3ncr0w
@b3ncr0w Жыл бұрын
That's exactly what I was looking for! Thank you so much : )
@rogerscript
@rogerscript Жыл бұрын
Jack, you are my superhero!
@beemanik
@beemanik Жыл бұрын
My first comment to you. Your videos is super useful and straightforward. I like using Redux, but Context is super for local high state around piece of tree. I wish you GL and thanks for sharing your experience .
@useeffect
@useeffect Жыл бұрын
Thank you Jack for really valuable React.js content on KZfaq !
@patrykkalinowski6979
@patrykkalinowski6979 7 ай бұрын
It was really good. Thanks a lot !
@maherbenbaccar
@maherbenbaccar Жыл бұрын
thanks @jack you are my favorite professor and all your vedio is amazing and good thanks a lot
@manuelpascual7063
@manuelpascual7063 Жыл бұрын
Jack, this is amazing content. I never thought about the idea to use this combination between context and useRef. You are such a huge inspiration 😊
@shiyaamcodes7428
@shiyaamcodes7428 Жыл бұрын
I was looking for this exact thing for the past two days!!!! Glad I found this
@fahmijabbar1595
@fahmijabbar1595 Жыл бұрын
Absolute meat!!! Thank you for the tutorial Jack
@javLG
@javLG Жыл бұрын
Thanks for this implementation, you're a beast Jack!
@kelvinklee
@kelvinklee Жыл бұрын
This is pretty awesome, I am curious how close a small lib like Zustand is basically just this general structure with a few more features? Good to see what's going on behind the scenes. Thanks for always sharing amazing content!
@fotoflo
@fotoflo Жыл бұрын
Thanks Jack! Came for the context, stayed for the typescript!
@loquek
@loquek Жыл бұрын
I really don't mind using Zustand and React-tracked for this (in-fact I love it), but nice still for a no-additional dependancies setup
@jherr
@jherr Жыл бұрын
Yeah, I use Zustand daily. But it is nice to have techniques like this in the back pocket.
@faviocabral2675
@faviocabral2675 Жыл бұрын
@@jherr Master Jack I can ask you something, what is better redux o context react Thanks.
@coldboyvic
@coldboyvic 8 ай бұрын
This is one of the best tutorials on KZfaq 🙌💯
@MuhammadAdnan-nj4it
@MuhammadAdnan-nj4it Жыл бұрын
good work king, love you
@fadfooood
@fadfooood Жыл бұрын
I will never do that but hey Jack now I understand what Zustand and other state managers do at a scale. Thanks!
@miguelblanco5563
@miguelblanco5563 Жыл бұрын
This is pretty awesome, I just implemented this on my work
@mikexcoder1508
@mikexcoder1508 Жыл бұрын
came here from Codecamp, awesome content. Subbed!
@motivateme2402
@motivateme2402 Жыл бұрын
Thank you Jack for the best content I've ever seen, you're a great and awesome guy, and You thought me a lot
@agk2011
@agk2011 Жыл бұрын
Thank you so much for such an amazing video. This type of content is really inspiring.
@MrChernicharo
@MrChernicharo Жыл бұрын
Woooah! I couldn't stress enough how much I loved this video! Thank you Jack! 🥳
@ThugLifeModafocah
@ThugLifeModafocah Жыл бұрын
This was on another level. I really hate Typescript. I know its advantages, but I hate it nonetheless. But I'm kind of obligated to use it, and your video show me how to do something that I needed and have no knowledge how to do it. Thank you.
@FidelGuajardo
@FidelGuajardo Жыл бұрын
Jack this is a compliment. You are the developer version of Last Man Standing. I think you can be called "Last Dev Standing" !!!
@jherr
@jherr Жыл бұрын
Last Man Standing? There are a lot of devs around. :)
@codebycarlos
@codebycarlos Жыл бұрын
This is incredibly helpful. Thank you!
@user-mw6ny9xy4r
@user-mw6ny9xy4r Жыл бұрын
Thank you Jack, I really love this content I`m going to adjust this on my toy project now awsome!
@pablocubicomusic
@pablocubicomusic Жыл бұрын
I see `useStore` is in the same scope as the components since they all live in the same file. But how could you extract useStore to use it in other places, splitting code into more failes?
@awefawefwaef
@awefawefwaef Жыл бұрын
Thanks Jack!
@Bookwala12
@Bookwala12 Жыл бұрын
Woah Jack, you are a magician and even after watching you so much, I still can’t wrap my head over some of your concepts.. humbling experience this video was.. I will come to it again a little later in life..
@MukulDuttshades
@MukulDuttshades Жыл бұрын
ReturnType was clever.
@user-cm7um1hg5c
@user-cm7um1hg5c Жыл бұрын
Wow, it's really awesome
@BNakato
@BNakato Жыл бұрын
Great stuff.. love these kind of videos
@mrmadhimk8753
@mrmadhimk8753 4 ай бұрын
Your cool Jack 🔥🔥🔥 Thank you ❤
@skandertebourbi357
@skandertebourbi357 Жыл бұрын
Thank you for this amazing content, really insightful.
@patrickkaipainen3301
@patrickkaipainen3301 Жыл бұрын
This is awesome. Been working on a dynamic form that can have any number of groups of several inputs each. The state for the entire thing lives in one provider. React.memo helps a bit with unnecessary renders, but this would work waaaay better.
@abdessittirharkati7603
@abdessittirharkati7603 Жыл бұрын
Stunning work
@cintron3d
@cintron3d Жыл бұрын
This is brilliant, thank you!
@jherr
@jherr Жыл бұрын
Thank you so much!
@avneet12284
@avneet12284 Жыл бұрын
Brilliant stuff, Jack !
@luizpaulonascimento9162
@luizpaulonascimento9162 Жыл бұрын
this is awesome
@TheOllieJT
@TheOllieJT Жыл бұрын
Love ot, more advanced content like this please!
@spectralapps1834
@spectralapps1834 Жыл бұрын
believe it or not, I created a package inspired on this video: npm i create-fast-context it's simply like: import { createFastContext } from 'create-fast-context'; //myContext.tsx const { Provider, useStore } = createFastContext(initialState); //initialState //component const [state, setState] = useStore(state => state.selector); //state selector //updating the store setState(prevStore => ({ user: { ...prevStore.user, isOnline: true }, })); thank you for the amazing video and tips. 🙏
@jherr
@jherr Жыл бұрын
I’ll check it out!
@ryanle4059
@ryanle4059 Жыл бұрын
Thank you so much, Jack. I've tried this technique without using react context. I use closure for the store and it works perfectly fine. I don't know if any downside to this approach. Thank you again for sharing great quality content.
@jherr
@jherr Жыл бұрын
Downside to that is that you can't restrict it to a specific part of the tree as you can with context. That may not matter to you. Also, that approach is very similar to Zustand, so you might want to try that because it's of the shelf and well supported.
Is the new React use hook a footgun?
22:20
Jack Herrington
Рет қаралды 60 М.
Mastering React Memo
26:56
Jack Herrington
Рет қаралды 134 М.
Prank vs Prank #shorts
00:28
Mr DegrEE
Рет қаралды 11 МЛН
娜美这是在浪费食物 #路飞#海贼王
00:20
路飞与唐舞桐
Рет қаралды 7 МЛН
what will you choose? #tiktok
00:14
Анастасия Тарасова
Рет қаралды 7 МЛН
3 React Mistakes, 1 App Killer
14:00
Jack Herrington
Рет қаралды 115 М.
Mastering React Context: Do you NEED a state manager?
37:26
Jack Herrington
Рет қаралды 98 М.
You're Doing React Hooks Wrong, Probably
20:11
Jack Herrington
Рет қаралды 64 М.
Why Signals Are Better Than React Hooks
16:30
Web Dev Simplified
Рет қаралды 472 М.
Don't Use React Context!! Use This instead
13:34
CoderOne
Рет қаралды 27 М.
Goodbye, useEffect - David Khourshid
29:59
BeJS
Рет қаралды 498 М.
Turns out REST APIs weren't the answer (and that's OK!)
10:38
Dylan Beattie
Рет қаралды 152 М.
State Managers Are Making Your Code Worse In React
13:33
Web Dev Simplified
Рет қаралды 178 М.
This is the Only Right Way to Write React clean-code - SOLID
18:23
Prank vs Prank #shorts
00:28
Mr DegrEE
Рет қаралды 11 МЛН