Preface
typia is a transformer library supporting superfast runtime validation, and JSON serialization function boosting up performanc...
For further actions, you may consider blocking this person and/or reporting abuse
I don’t get the point of the article, all you’ve proven is that a library hyper-optimized for Node and taking advantage of its hidden features doesn’t work well on Bun. No surprise there. The title claiming that this applies to all logical operations is nothing but clickbait.
The validation and serialization code uses below expressions, and you are saying that these common expressions are hyper optimized only for NodeJS so that have not to use in Bun, right?
One very little detail was coincidentally omitted: the OP of this post is the creator of the Typia library and there's a chance they are biased in promoting their hard work. I will believe it when a benchmark is made by an unbiased non-related third party.
Why to check types in runtime? Isn't it most idiotic idea ever?
Request body data validation is the most famous case of runtime validation.
nestia.io/docs/core/TypedBody/
Oh no
You get unknowns (often any) from libs, external Apis (even if they claim their contract), raw SQL queries... Keep on adding cases when type is only on the paper
At these cases it's way safer to validate data before using it
This is not what AOT compilation means, and all JIT engines perform some type of “hidden class optimization”, though you need to have enough runs to make it hot.
From my experience, if you happened to create your own benchmark program, 90% of the time the problem is there.
At any rate, I would create an issue at on GitHub for bun and see what they say.
Can you show the repo what actually you are trying to do . Typia i don't see the starter repo for that to explore .
Would be an awesome benchmark to add to github.com/moltar/typescript-runti...
What about in Deno 🤔❓
It's good there
nice work on typia 👍
i havent tried it myself but it seems to me that the benchmark is legit.
i hope the bun maintainers catch wind of this but im not sure if they can address this.
either way their github issues is flooded so i am not holding my breath.
I wonder whats the state in Deno2
What do those numbers in the the charts represent? Milliseconds?