Another question, how are people actually using Typescript with Svelte? It seems like you can't use $some.prop = avalue, it can't be type checked, so wtf is the point of using Typescript with Svelte?
To each their own, but I think life's too short to be adding types to your view logic and your templates. It adds so much complexity for so little gain. Maybe it'll get better at some point where it will change my mind, in particular when using something like Deno.
Does it type check templates yet?
Webstorm now properly supports template type checking too https://blog.jetbrains.com/webstorm/2021/11/webstorm-2021-3/...
Vue 3 looks a lot better than Vue 2 but honestly it's just playing catch up to React. I don't know why you'd choose it.
React is not the end-all, nor will it ever be, as long as there are interesting new projects coming out, and neither is Vue or Svelte. My website uses React, but personally I would rather use Vue or Svelte in the future.
> Wikipeida chose Vue
Yeah their reasons look very much like dubious attempts to justify the choice someone has already made.
1. You can use it without a build step.
Sure, but only if you're not using Typescript, which would be mad. A build step is a mild inconvenience. Not something that should cause you to choose a worse solution (though they do also use PHP so they're probably used to bad tech).
2. Vue.js may enable us to rely on fewer libraries as dependencies.
Ha! When I added Vue and its required CLI stuff to our package.json it pulled in around 1000 dependencies. React has like 4.
3. The official Vue libraries are evolving in a stable and predictable fashion.
You can still use React classes if you want to. They're not deprecated. It's unlikely they ever will be.
4. Vue.js development is not led by a single corporation whose goals may diverge from those of the WMF.
I mean... come on.