Fair enough and you seem to be adding features fairly quick which is impressive to watch, but my point still stands.

These benchmarks don't make me think Bun is fast, they make me think Bun is cheating in something they don't need to cheat in yet.

Go heads down, finish adding features, run another benchmark when you're closer to parity and promote THAT heavily. Sure it won't be such a dramatic difference once you have to compare apples to apples but it'll be more honest.

Here’s another perspective on this: someday, you’re going to find bugs that require more code to work correctly, and more code is slower. If you’ve fixated on performance you now have a conflict of interest, and conflicts make it easier to talk yourself into bad solutions.

I say this as someone who has gotten a lot of pushback in my career about performance work. Performance is a thing that needs to be priority. It doesn’t trump all else.

Make it work, make it right, make it fast. When people skip step 2 (and a godawful number of people do) they make enemies of themselves to their coworkers.