21–30 of 404 posts
I'll be the first to mourn the (future) loss of $: but the video clearly shows that the changes are a pretty enticing way to make your code that little bit cleaner, and solve all of the "but Redux!" style questions. Svelte for Apps. Svelte for Sites.
I think a real type system (i.e. compiler checked, rather than relying on falibilities of human programmers) would be a better solution. If Svelte already has a compiler why not implement this as part of it?
Perl called these sigils. They were incredibly useful and powerful, but the dev community decided that they hated them.
"Like every other framework, we've come to the realisation that Knockout was right all along." Nope, nope. Been there, done that, with 2-way data binding and never going back.
But if these guys are only now reaching Knockout, I still have to wait for them to catch up to Backbone.js, I guess.
Svelte slowly shapeshifting into jquery. Day after day, methodical evolution.
Apart from the superficial use of the $ sign, what else is jQuery about any of this?
"Like every other framework, we've come to the realisation that Knockout was right all along." Nope, nope. Been there, done that, with 2-way data binding and never going back.
I thought that quote of yours was a sarcastic overview you yourself had written but no, it's an actual quote from the article! > Like every other framework, we've come to the realisation that Knockout was right all along. > Svelte 5's reactivity is powered by signals, which are essentially what Knockout was doing in 2010. More recently, signals have been popularised by Solid and adopted by a multitude of other framew…
I'll be the first to mourn the (future) loss of $: but the video clearly shows that the changes are a pretty enticing way to make your code that little bit cleaner, and solve all of the "but Redux!" style questions. Svelte for Apps. Svelte for Sites.
I'm not going to miss $, I've found it to be a weirdly documented nightmare...
I found `$:` to be extremely confusing, full of weird quirks, and completely turned me off to using svelte for anything more than basic sites.
Runes seem like a clear improvement, but brings Svelte a step closer to React -- which hurts its appeal to me.
The difference between `let counter = $state(0)` and `const [counter, setCounter] = useState(0)` is near its initial value -- zero.
I do love the view library competitive landscape and enjoy seeing different paradigms leveraging reactivity. I also like the compiler optimizations that Svelte is bringing to the entire ecosystem.
I wrote my initial thoughts on sveltekit when I built neovimcraft: https://bower.sh/my-experience-with-svelte-kit