Comments by "Okie" (@okie9025) on "" video.

  1. I like to think of React as a component-building library, while Svelte is a website-building framework. Svelte is obviously better at building traditional HTTP HTML websites, because that is what it specializes in, but it definitely cannot replace React. IMO React has a way better syntax for defining general components and using them. Also React doesn't really have anything to do with the web, it's just a diffing library. You can use React to make TUI apps using react-ink, or make mobile apps using react-native. React is a very simple way to represent UI and that's why it's almost universal.
    12
  2. 1. The nature of Svelte makes it so that minimizing your dependencies is very easy, unlike in React where some projects would literally be impossible to make if some of the more popular dependencies didn't exist. Popularity isn't really that big of a concern in Svelte. 2. Svelte is strictly targeting the web, unlike React which tries to be a general-purpose component-building library. This means that it's going to naturally have a larger growth in the web world, since building traditional HTML websites using Svelte is way easier and feels more natural. 3. To add to the point above - Svelte is not that good for purposes other than building websites. Don't expect Svelte competing with react-ink and react-native.
    5
  3. ​ @fakenameforgoogle9168  IMO Svelte is very obviously tied to the traditional web ecosystem. This is evident even in the terminology they use: it's not "screens" or "components", it's pages. It's not a "web app", it's a website. And here are the major selling points of Svelte: - reduced JS bundle size - progressive enhancement (making your website work with/without JS) - easier use of HTML web standards like form actions and serverside rendering - better SEO. Notice that basically none of these features are applicable to any platform other than the web. React, however, tries to be as lean as possible. The React team to this day has made sure not to include anything web-related in their library, so that it can work as a general purpose component language.
    3