I don’t think they’ll consider your framework at this point because it doesn’t have enough mindshare. I don’t think they’re being unfair or blacklisting you. Also, your PR was very forward and assumptive IMO, “can I get an issue number” like you’re entitled to one. Get some more users (stars being a proxy for that), and I’m sure they’ll consider you if you ask with a little more humility.
“Way faster” is a bit hyperbolic isn’t it? 2.5 times faster? That’s no order of magnitude. What validation use cases are there where it makes a difference? Very few.
Here’s the thing: if people really want fast validation and transformation, they’re probably not going to use python. People use python for its developer ergonomics and experience. Dicts as a configuration DSL are inferior to classes and type hints for very simple reasons
1. One bad thing about python is that both single and double quotes are acceptable. Dicts are built with strings, so there’s an anxiety about having to standardize in one over the other that adds to cognitive overhead.
2. There are dict literals that get rid of one string, but again, just another “choice” people don’t care to make if they don’t have to
3. Curly brackets aren’t the easiest things to type relative to other characters.
4. Curly brackets are extremely difficult to pair if you don’t have an editor that does it automatically or if your code formatter puts many brackets on the same line.
There is no need for hostility.
My comment was in your response of the benchmark that pydantic is fastest.
In their own documentation they invite all other framework to send their results.
That said what pydantic team does is up to them, the Maat was made before pydantic was a option, it has filled that usecase.
The benchmark was only added because of a internal discussion about which tool to use.
Engineering is about tradeoffs and each project will have own technical problems. Therefor there will never be the best solution, only the best solution for a particular problem within that context.
