Consider whether to limit the benchmark target to go-playground

[sivchari]

Currently, we write benchmark against other all library (go-playground/validator, asaskevich/govalidator, go-ozzo/ozzo-validation and gookit/validate), but the project maintained actively seems to be only go-playground/validator.

I start thinking it's good to only write benchmark against go-playground/validator.

I want to listen other feedback. If you have time, please comment your thought here.

cc. @BlackBuck @taua-almeida

[taua-almeida]

go-ozzo/ozzo-validation should be out for sure, last commit was 5 years ago, not even in maintenance mode any more.
gookit/validate I would still keep since they are still maintaining and the issues sections seems to be pretty active still.
asaskevich/govalidator is in the middle between maintaining and keeping it alive but not as active as gookit/validate nor is adding new features in a while.

With that said, I would vote to remove go-ozzo/ozzo-validation for now, and keep the others but with a cadence check for asaskevich/govalidator since it could be potentially removed soon too.

[sivchari]

@taua-almeida
Thank you for good feedback. I totally agree with you. So let's still keep benchmark tests of go-playground/validator and gookit/validate So the plan it following.

• Delete go-ozzo/ozzo-validation benchmark tests and remove dependency from go.mod, then remove it from doc and README
• Delete asaskevich/govalidator benchmark tests and remove dependency from go.mod, then remove it from doc and README

@taua-almeida @BlackBuck
Please let me know if I overlooked something.

[BlackBuck]

@sivchari Do you think we can keep `asaskevich/govalidator till the next major release? It's a good benchmark to test against our validators. And since while we're adding more of them, we may keep it around for one or two feature releases.

WDYT?

[sivchari]

@BlackBuck
Yes, we don't need to delete these benchmarks all at once. We can do it step by step.

[sivchari]

At first, let's remove ozzo-validation!

[BlackBuck]

@sivchari
Would you like for me to draft a PR?

[sivchari]

Sure!

[sivchari]

Reopen to track other item.