[matthewmacleod]

Frameworks and their abstractions tend to evolve out of what we find people need to use in the real world when building their applications.

Context is generally a pretty powerful thing when used properly, and allows developers to build nice, readable code in more complex applications by extracting some of the complexity elsewhere, while maintaining a conceptually clean model. It's already used in common libraries like React Router, and establishing a first-class API for it seems like a good move in general.

And remember – if it's not useful for your particular use case, don't use it!

[weego]

Frameworks evolve out of a single group of people's needs. Unfortunately once the entire world gets involved they often end up including every possible need anyone could have.

[spraak]

> they often end up including every possible need anyone could have.

I don't think that's what is happening here with React. It'd be much different than it is already if that were the case, but instead it's stayed pretty lean