Hacker News new | ask | show | jobs
by wirahx 1009 days ago
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.

1 comments

I'm not going to miss $, I've found it to be a weirdly documented nightmare...
I originally created https://neovimcraft.com in Svelte to learn how it works.

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

As we've taken to saying around the virtual Svelte offices:

> The magic of Svelte isn't `let count = 0`, it's `count += 1`

That part hasn't changed!

Yeah I gotta agree. No comment on runes but $: was so weird that I was immediately confused at why I would try and use svelte for anything