Hacker News new | ask | show | jobs
by ramesh31 861 days ago
> We want Svelte to feel magical — we want you to feel like a wizard when you're writing Svelte code... So when we design things we need to think about the people who haven't read the docs in a while, if at all, and don't care about things like that. This means that things need to be intuitive, that we shouldn't need to worry about manual optimisations like memoisation, that we should have as few APIs as possible, and that things need to be discoverable

Amen. After being forced into working on a large Vue project as a React dev who had sworn it off, I've slowly come around to falling in love with it. Once you get over the "black magic" of it all, the productivity is insane. For people who just need to get things done, and couldn't care less about millisecond level rendering benchmarks, I would easily suggest it over React at this point.

2 comments

What makes Vue "insanely" more productive than React ?
>What makes Vue "insanely" more productive than React ?

React is a fantastic rendering library but there are no great React frameworks. Next is ok, but it's a beast that most people don't need. The beauty of something like Vue is having your batteries included in a standardized way that you don't have to worry about when upgrading, while also still being fairly lightweight. The average React app becomes a hodgepodge of dependencies that get frozen in time due to the fragile nature of NPM. Versus having a known and documented upgrade path for your router, state, styling, etc.

Vue is a unified ecosystem of tools written by the same authors and designed to work with one another. React gives you way more rope to hang yourself. Good luck figuring out what the routing and state management flavor of the minute is.
Then you're looking for Next.

It's a unified ecosystem of tools written by people closely related and désigned to work with one another.

I'm not looking for Next. I'm quite happy with Vue or Sveltekit.
Vue benchmarks better than react anyway.