PrinceJS: Benchmark Corrections and Lessons from a 13-Year-Old Developer

1 comments

• lilprince1218 1 hour ago
  After my original post, the Hacker News community helped me identify critical issues with my benchmarking approach. Here's what I learned:

  The Problem:

  I used autocannon for benchmarking, which can't handle Bun.serve speeds (as pointed out by Elysia's maintainer)

  Made exaggerated performance claims

  Had security vulnerabilities in JWT implementation

  The Fix:

  Switched to oha for accurate benchmarks: 21,748 req/s (placing PrinceJS among top 3 Bun frameworks)

  Fixed all security issues

  Removed "fastest" claims, now positioning honestly as competitive

  Technical Details:

  Real oha results: Elysia (25,312), Hono (22,124), PrinceJS (21,748), Express (9,325)

  Running on Windows 10 with: oha -c 100 -z 30s

  Next step: Cloud VM testing for consistent, reproducible benchmarks

  The framework is now more honest about its capabilities while still delivering competitive performance. Lesson learned: accuracy and security matter more than impressive numbers.

  Try it: bun add princejs

  GitHub: https://github.com/MatthewTheCoder1218/princejs