Live data from Hacker News

4.0M tokens for Next.js vs. 2.5M tokens for Wasp: same app, same prompt

wasp.sh

1–2 of 2 posts

Re: 4.0M tokens for Next.js vs. 2.5M tokens for Wasp: same app, same prompt

#2
Interesting that we're now seeing tokens/task become a huge factor in what framework to use. In the past, it was often dev happiness to choose a tool. But if you're not writing the code anyway, you should optimize for tokens/task assuming other things such as performance are equal.