I would like to extend this point of view with my own. A fragmentation of the ecosystem over several libraries remains for me a very good approach in the long term where the choice of the users is built not on “trending” which would force us to make only “default” choices but on a pro-active approach which implies a small learning curve and which, above all, results in the empowerment of the user on his choice - which for me, remains essential in the design of a software.
There are always several approaches to solving the same problem and the multiplicity of solutions basically pushes us to refine the problem to learn, understand and finally be aware (with all that this implies) of our choice. This may take more time, it certainly requires more effort, but this approach makes us less prone to software entropy and a multiplicity of levels that ultimately leads to a disempowerment of bugs and security holes (because we no longer know who or why we made a particular choice).
More broadly, a monopoly situation of one library on a given problem (and therefore the default choice) is never a good thing for a given ecosystem 
.