<story><title>Comparing Svelte and React</title><url>https://www.jackfranklin.co.uk/blog/comparing-svelte-and-react-javascript/</url></story><parent_chain><item><author>deckard1</author><text>I&amp;#x27;m a big fan of Svelte. I&amp;#x27;ve raved about their documentation before, but it bears repeating: this should be the gold standard. You can read it all in a day. There are examples to follow right next to the documentation.&lt;p&gt;Svelte is both succinct and powerful. I find this in contrast to React which is often baffling and incoherent. I say this as someone that has used React professionally for 6 years. They&amp;#x27;ve changed their mind at least 3 times on the API and none of it fits together today. Hooks and classes don&amp;#x27;t mix, lifecycle methods are still out there and just as confusing today as they were years ago. Mixing state and functions. It&amp;#x27;s just a horrible bag of half-baked bad ideas. And it&amp;#x27;s not even batteries included.&lt;p&gt;Svelte has it all built-in. It has the equivalent of CSS modules. It has global reactive state and an incredibly simple state protocol that seems almost stupid if you&amp;#x27;re coming from Redux. You step out of your daze and realize you don&amp;#x27;t need all the rituals and boilerplate. The things I&amp;#x27;ve seen built on top of that simple protocol can be incredible. It&amp;#x27;s not magic. It&amp;#x27;s just JavaScript.&lt;p&gt;I dare say that Svelte is a joy. But I hesitate to even leave this comment here. Because I know the architecture astronauts are listening, eager to sink their claws into this simple elegant new thing and fill up their Github profiles with soon-to-be abandonware cruft which they will use to pad out article after Medium article which will all pour down upon Hacker News like a shit typhoon. Prodding us to join their cult of Svelte+RxJS. Or Svelte Sagas. Or their random dogma they toss into a giant bucket labeled &amp;quot;Svelte best practices.&amp;quot; And, of course, &amp;quot;Ten ways you are doing Svelte wrong.&amp;quot;&lt;p&gt;I might be a little bit cynical.</text></item></parent_chain><comment><author>jeswin</author><text>But I wish new frameworks stayed away from inventing new language syntax. Not only is it a cognitive burden on programmers, it throws all the tooling off.&lt;p&gt;From Svelte: {#each cats as { id, name }, i}&lt;p&gt;JavaScript already has facility for loops and mapping, and relying on that will automatically get you tooling&amp;#x2F;IDE support. React handles this aspect quite well, and to me that&amp;#x27;s a point in favor of React.&lt;p&gt;I do agree with your post - especially on hooks being a step backward.</text></comment>
<story><title>Comparing Svelte and React</title><url>https://www.jackfranklin.co.uk/blog/comparing-svelte-and-react-javascript/</url></story><parent_chain><item><author>deckard1</author><text>I&amp;#x27;m a big fan of Svelte. I&amp;#x27;ve raved about their documentation before, but it bears repeating: this should be the gold standard. You can read it all in a day. There are examples to follow right next to the documentation.&lt;p&gt;Svelte is both succinct and powerful. I find this in contrast to React which is often baffling and incoherent. I say this as someone that has used React professionally for 6 years. They&amp;#x27;ve changed their mind at least 3 times on the API and none of it fits together today. Hooks and classes don&amp;#x27;t mix, lifecycle methods are still out there and just as confusing today as they were years ago. Mixing state and functions. It&amp;#x27;s just a horrible bag of half-baked bad ideas. And it&amp;#x27;s not even batteries included.&lt;p&gt;Svelte has it all built-in. It has the equivalent of CSS modules. It has global reactive state and an incredibly simple state protocol that seems almost stupid if you&amp;#x27;re coming from Redux. You step out of your daze and realize you don&amp;#x27;t need all the rituals and boilerplate. The things I&amp;#x27;ve seen built on top of that simple protocol can be incredible. It&amp;#x27;s not magic. It&amp;#x27;s just JavaScript.&lt;p&gt;I dare say that Svelte is a joy. But I hesitate to even leave this comment here. Because I know the architecture astronauts are listening, eager to sink their claws into this simple elegant new thing and fill up their Github profiles with soon-to-be abandonware cruft which they will use to pad out article after Medium article which will all pour down upon Hacker News like a shit typhoon. Prodding us to join their cult of Svelte+RxJS. Or Svelte Sagas. Or their random dogma they toss into a giant bucket labeled &amp;quot;Svelte best practices.&amp;quot; And, of course, &amp;quot;Ten ways you are doing Svelte wrong.&amp;quot;&lt;p&gt;I might be a little bit cynical.</text></item></parent_chain><comment><author>alfonsodev</author><text>I think many people adopted React because Facebook was behind it, and using it in production, the ecosystem is huge, there is a react- package for everything you can image, there is also react-native, I don&amp;#x27;t like it, but there it is, you can reuse the knowledge to build native mobile apps.&lt;p&gt;Now Svelte, I haven&amp;#x27;t been following, but I think the creators are working in what&amp;#x27;s going to be next and even better framework[1], to your point of things in Svelte not changing as much as in React, maybe it just a matter of time.  
Here is the video I had in my bookmarks for a while, I still couldn&amp;#x27;t make the time to watch, so I hope my comment is not too far from reality.&lt;p&gt;[1]&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=qSfdtmcZ4d0&amp;amp;t=875s&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.youtube.com&amp;#x2F;watch?v=qSfdtmcZ4d0&amp;amp;t=875s&lt;/a&gt;</text></comment>