Are you saying one cannot use a "component approach" without React? That's like saying I'm denouncing cars cause I don't like Chevys.
When you are into programming, like we are, you think of these things long before some big company tells you what to do.
Where I work, we use React because it's easier to find new hires (because they want to work with React) and quicker to get them up to speed on a project (because they already know the framework).
It's also easier to integrate and extend any 3rd party components, as we're already familiar with the boilerplate.