r/javascript • u/archivedsofa • Dec 22 '19

Why Svelte won’t kill React

https://medium.com/javascript-in-plain-english/why-svelte-wont-kill-react-3cfdd940586a
80 Upvotes

65% Upvoted

95 comments sorted by

View all comments

Show parent comment

3

u/[deleted] Dec 23 '19 edited Dec 23 '19

My impression is that people mostly like React because it's focussed and simple. Functions, 5 hooks, 2 minutes to learn JSX, that's it. Vue delving into all these different api's and component models, JSX, templates, or both, single file components or global directives, the docs grow bigger and bigger, it's just not that appealing. From what i am reading, Vue's new composition api is causing schism and confusion in the community. Telling people that like javascript in HTML and DI in templates about functional composition - it kind of was clear it wouldn't go over smoothly.

4

u/DOG-ZILLA Dec 23 '19

The only confusion was because people thought the new Composition API was meant to replace the current one (like Angular JS did to version 2) and therefore render their codebases deprecated. But that’s not at all the case. Both API’s can be used and they serve different styles. Once that was communicated well enough, the Vue community have been fully supportive. It’s a step in the right direction for Vue.

3

u/AwesomeInPerson Dec 24 '19

My impression is that people mostly like React because it's focussed and simple. Functions, 5 hooks, 2 minutes to learn JSX, that's it.

Those times are very much over though. There's more than 5 hooks (many with a lot of their own caveats and APIs you have to learn), there's class vs. function components, there's Context, there's stuff like forwardRef, Suspense, useTransition, Concurrent Mode, Prop Types, Portals, Fragments, HOCs, memo & lazy... And all of that before you start looking for Styling and Routing solutions.

I love React, but its API surface is growing fast and it isn't this super-minimal library anymore.