I know there's very good reasons for the changes, but it feels so similar to React (and even hooks) now that I don't see any big positives to using Svelte vs just using React. Sorry Rich.
I feel the same way, but after watching a couple of the videos Rich has put out I thought the main driver for the change were the “gotchas”. I have not done production Svelte development so I never really dealt with any of that. Given you’re background, are the caveats/pitfalls he mentions not common to your projects or do you just view the critique as newby problems?
My favorite thing about learning Svelte was that it has my favorite "documentation" of any library. It's just a list of code samples showing various different scenarios [0]. This made it dead easy for me to understand its way of doing things without needing to get too deep into the methodology.
Honestly, the biggest thing with all of these systems is what library support do they have beyond the core? I specifically need a good component library, and want to do things with Three JS. Svelte had that covered.
Any recommendations for building SPAs that can last a decade without constant rewrites?
There's nothing stopping you from staying on an old version of Svelte or React, you just won't have access to all the new goodies and the surrounding ecosystem.
To add to the other comment, Mithril.js is another frame work that hasn't changed much for the last 7 years.
Every non-dead project is evolving and is adding new things. Even behemoths like Java or C++. But maybe Ember.js is technically not dead and is mostly the same? I don't know, it's bad and I prefer rolling with the tide.
This is classic React!
However, I don't really know why he thinks classes are awesome without inheritance, either. Once you do away with inheritance, what's the benefit over writing a function that builds an object? Get rid of the middle man, the extra keywords, the prototype chain, etc., and go with a function. Did I miss something?
I don’t disagree, but I never got to hear/read his thoughts on that subject.
And yeah - I like the idea of defending any use of classes instead of reaching for them to brush your teeth. Some places (my current place) will reach for classes all the time without even the excuse of bundling state.
I picked up Svelte 3, and 4 last year and used it to build many browser extension UIs.
I really enjoyed my time with Svelte but I found it did not scale well. Maybe that’s a me problem though.
I’ve since switched over to using React, and I’m really enjoying writing React. NOT working with others React code though, that still sucks.
But I’ve actually switched to using React for my browser extension UIs. Prefer it
