Prototype VS react-context

It's very weird to realise that this isn't long enough to remember a time when extending native prototypes was en vogue. Source: over 1 year ago

The parent is referring to the Prototype framework (http://prototypejs.org/), not the JS language concept of a prototype. Source: over 1 year ago

Let's not forget about http://prototypejs.org/ & http://script.aculo.us/ for modern Web 2.O. - Source: Hacker News / over 2 years ago

Overriding prototypes used to be state-of-the-art, and indeed it was one of the things that made me fall in love with JS. Frameworks like PrototypeJS and MooTools were built around this and it was of very limited convenience and unlimited headaches. Source: about 3 years ago

The context API is generally used for managing states that will be needed across an application. For example, we need our user data or tokens that are returned as part of the login response in the dashboard components. Also, some parts of our application need user data as well, so making use of the context API is more than solving the problem for us. - Source: dev.to / 5 months ago

Previously, in the legacy docs, the Context API was just one of the topics within the Advanced guides. Unless you went digging, you wouldn't have been introduced to it as one of the core ways to handle deep passing of data. I really like that, in the new docs, Context is recommended as a way to manage state as its one of the best ways to avoid prop drilling. - Source: dev.to / about 1 year ago

You can read more about the Context at https://reactjs.org/docs/context.html. - Source: dev.to / about 1 year ago

You need to use something like Redux or the React Context API. Source: about 1 year ago

If you don't know what a provider is, visit the react docs. - Source: dev.to / over 1 year ago