If the post does not have any use-cases proving value then perhaps this is something yet to be validated, i.e. the burden on the users, not the creators.
In an era where creating such libraries is much cheaper than validating that they're useful or work, yeah you really should validate it before you expect someone to use it. Nobody is going around trying out every slop project they see, they'd be wasting hours and hours for no gain at all.
This all being said, I do find the idea interesting, but heeded it's advice when it said it's hideously expensive and risky to use. So yes, I do want someone braver, richer, and stupider than me to take the first leap
Wym? I can slop out 100 libraries/frameworks/packages/cli's a day, the onus is not on other people to prove that they are useful.
Corollary: if the post does have use-cases providing value, this is something yet to be validated and the value is just imagine by the author
Why would the onus on the value prop be on the user?
There should be no shortage of examples the creator could provide, unless of course...