3 ms·
It might interest you that Wikipeida chose Vue to modernise its frontend in the future [1]. Different frameworks offer different benefits and different downside
by marcus_cemes 5y ago
It might interest you that Wikipeida chose Vue to modernise its frontend in the future [1]. Different frameworks offer different benefits and different downsides.
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.
[1]: https://phabricator.wikimedia.org/T241180 https://phabricator.wikimedia.org/T241180
- IshKebab 5y agoYeah we chose Vue at work too, but it was only because we didn't have enough experience of either. > 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.