>You can say that about any library; it has nothing to do with the popularity, support or quality of the particular dependency. If the technical decision makers choose not to use something you like then you won't get to use it.

The "technical decision makers" though has very much to do with the "popularity, support or quality of the particular dependency".

If a dependency is popular then more technical decision makers at more companies will be using it, and the more choices one that likes/wants to work with it has for a job.

>This is one of the key reasons to climb your career ladder. If you climb high enough you get to be that decision maker.

Which will make the point moot, as they wont be the one coding using the technology anymore.

Example: a company is using Angular 1 today and looking to modernize their stack. You have been hired, and one of your first tasks is to pick a new framework and convince the rest of the team that it's the best choice. You're thinking about the following options:

1) React 2) Vue 3) Angular 2+ 4) Aurelia

If your preference is 1) or 2), it shouldn't be too difficult, even though it means a complete rewrite or building in-house adapters to migrate gradually. If it's 3), even though similar adapters exist, good luck convincing anyone. If it's 4, you're basically dreaming.