But there's no way to twist that around into "minitest devs are the ones that suck by their own logic".
Either nobody here sucks at coding, or some test-writers suck at coding. But those are the only two options that make sense.
What you're saying, is also just an opinion.
When I say your disagreement with them is an "opinion", I am not using that definition. I'm using a much more narrow definition. You have different ideas of what makes code good. Different preferences.
While my argument is not based on my preferences. When I called those tests bad I was just explaining the point. It doesn't actually matter if I think the tests are bad or not. Either way the minitest devs are absolved of their own criticism.
If you would like me to use a different word than "opinion", you can suggest one. The point is, please understand what I mean, and let's not argue about how to define words.
If misunderstanding is possible then clearly it's not simple to understand what people mean everytime. Maybe if you explained more clearly I'd understand why you feel your opinion is factual and feel what I say is just opinion.
> my argument is not based on my preferences[...] It doesn't actually matter if I think the tests are bad or not.
The thing I am calling your opinion is not your evaluation of minitest. I'm saying your evaluation of the test code is an opinion. My evaluation of the test code is also an opinion.
Neither of our opinions about the test code matter here.
That was what I was arguing in this post: https://news.ycombinator.com/item?id=34831045
I don't think your attempt to turn things around into criticism of minitest is an opinion. I think it's snark that doesn't work when examined more closely.
Not because you can flip the standard around and say it sucks for those same reasons it accuses some tests of sucking.
The stuff you said up here: https://news.ycombinator.com/item?id=34829343
is just wrong.
It "sucks" because it has an inaccurate method name that implies an inferiority. This is my current and original criticism of the minitest devs.
Your idea that I am unprofessional, is an opinion.
"This method name indicates a lack of understanding that finding the right balance of speed, cost and quality is a compromise."
No I am not.
But that's different from writing code that sucks. A single flag name like that doesn't even affect functionality or readability.