3 ms·

This is what happens when bored developers just have to improve something that doesn't need improving.

• disintegrator 3y ago
  I think Rich clearly demonstrated the pitfalls in today's Svelte and the introduction of runes seemed like a great solution to them. I'm not a Svelte user but this new feature does seem clearer to me when looking at the refactored code than the magic reactivity behind the `$` syntax. Overall a net win in my opinion.
• rich_harris 3y ago
  Svelte 3 came out in early 2019, and the framework hasn't really changed much in that time — one thing we can't be accused of is making changes for changes' sake. But since then, the front end community has discovered valuable new ideas and techniques. Meanwhile, people have encountered the limits of the Svelte 3 approach. Svelte is really good at solving most of the problems you throw at it, but it's not perfect. The changes we announced today are _necessary_. If you're not convinced, I encourage you to watch this video, where I talk about why that is: https://www.youtube.com/watch?v=RVnxF3j3N8U https://www.youtube.com/watch?v=RVnxF3j3N8U
  • pbowyer 3y ago
    That's a great - and funny - video. Nicely done!
• danaw 3y ago
  Always gotta be someone like you in the crowd eh? Perhaps, just perhaps it's a good change for a lot of people?
• jraph 3y ago
  I was a bit apprehensive reading the comments here, but reading the presented changes, I'm actually quite happy. I built two Svelte apps. I liked using Svelte but was a bit annoyed by the aspects these changes are fixing. The code also seems easier to write and to understand. My feeling that the Svelte team has taste is strengthened.