Are there downsides when library writers build and publish both .so and .a files, and the library users can pick if they want to link statically or dynamically?

If so, which downsides are those?

I can't tell if they exist, and it seems to me that this is a flexible solution that gives the power of choice to the consumer of the library.