Why not use smallcheck?

I had opened an issue Can we un-obsolete this? I have use cases. · Issue #58 · Bodigrim/smallcheck back in July 2025, but Andrey @Bodigrim declined to consider my arguments. I was just regretfully mulling over that conversation in my mind earlier today, thinking about how I could argue my position better. Over time, I have come to believe that this is not a technical matter but a matter of respect.

I believe randomized and exhaustive checking are two complementary, orthogonal approaches, and progress made in one, while a cause for celebration, cannot render the other obsolete. Practically speaking, I shall still use SmallCheck, and I consider this obsolescence warning a kind of a Yellow badge - Wikipedia that de-legitimizes me as a user of Haskell and a contributor to the Haskell ecosystem. The argument of Weak Men Are Superweapons | Slate Star Codex applies. First they mark the package you like as obsolete, then they decline to engage in a conversation with you, and where this is going is that finally they will abandon the package altogether.

I think, however, that this issue is a manifestation of a general trend of maintainers having no respect for and no sense of honourable obligation towards users. Not to engage in a good faith technical discussion, and not to maintain the packages they are the maintainers of. «As a maintainer, I declare this package unworthy of my effort to maintain it. My great wisdom and experience grant me the privilege to disregard any and all objections on this matter.» This kind of attitude erodes whatever ambient good faith is still present in the Haskell community.