?? 'fast' and 'fully typed APIs' do not explain anything at all.

Those are completely generic descriptors.

Those are arguably 'differentiators' to the problem they are solving, but they don't first explain the problem they are solving.

> they don't first explain the problem they are solving

I think you're right about this and the "hero text" on their landing page should explain that in one crisp sentence. I imagine the authors of the project just aren't good at this stuff so hope they read this thread and refine the messaging.

It doesn't need to be in the 'hero text' it just needs to be somewhere.

What is cutting edge about it? What gaps is it lacking, and why not put thodr in more established tools? Basically, what problem is this solving and way throw out years of experience in the other tools?

Vite does not throw out any experience. It builds upon Rollup, esbuild, and other existing tools.

There's a great page on how it's cutting edge here: https://main.vitejs.dev/guide/why.html. I suggest you try using it to see for yourself.

Why Vite explains this all https://vitejs.dev/guide/why.html

Why would anyone read a long-winded technical article before they even know what they are about read about?

"We have some amazing fast tech, that will make your life better -> read our white paper! We have good APIs"

Tell people what it is first, roughly what it's for, then the benefits. Then the article.