5 ms·

They actually do right in the hero section of the landing page. For me: - fast (very important) - Fully Typed APIs (very important) Just those two points woul

by exhaze 4y ago

They actually do right in the hero section of the landing page. For me: - fast (very important) - Fully Typed APIs (very important) Just those two points would convince me to try it and I can see it right away on the landing page. At my company, I looked at Vite 6+ months ago and decided it doesn't make sense for us, yet, because of some specific tooling gaps, but it's a tool that I consider "cutting edge" in the frontend tooling world. I think they're doing just fine and their page doesn't have any major issues with their copy. Do you actually do frontend dev?

quest88 4y ago
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?
- Rapzid 4y ago
  Why Vite explains this all https://vitejs.dev/guide/why.html https://vitejs.dev/guide/why.html
  - jollybean 4y ago
    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.
- sachinraja 4y ago
  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 https://main.vitejs.dev/guide/why.html. I suggest you try using it to see for yourself.
jollybean 4y ago
?? '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.
- exhaze 4y ago
  > 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.
  - jollybean 4y ago
    It doesn't need to be in the 'hero text' it just needs to be somewhere.

by exhaze 4y ago

quest88 4y ago

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?

Rapzid 4y ago
Why Vite explains this all https://vitejs.dev/guide/why.html https://vitejs.dev/guide/why.html
- jollybean 4y ago
  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.
sachinraja 4y ago
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 https://main.vitejs.dev/guide/why.html. I suggest you try using it to see for yourself.

jollybean 4y ago

?? '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.

exhaze 4y ago
> 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.
- jollybean 4y ago
  It doesn't need to be in the 'hero text' it just needs to be somewhere.