Svelte: $derived can now be overwritten
github.com
Svelte: $derived can now be overwritten
1–10 of 55 posts
Re: Svelte: $derived can now be overwritten
#2As someone who has not used Svelte 5: What is the significance of his change?
Re: Svelte: $derived can now be overwritten
#3As someone who has not used Svelte 5: What is the significance of his change?
Re: Svelte: $derived can now be overwritten
#4People who have migrated a large enough production codebase to Svelte 5, what's your devex like?
Re: Svelte: $derived can now be overwritten
#5People who have migrated a large enough production codebase to Svelte 5, what's your devex like?
[dead]
Re: Svelte: $derived can now be overwritten
#6Wow, the optimistic UI example is so simple: https://svelte.dev/docs/svelte/$derived#Overriding-derived-v...
I wonder what Ryan Carniato, the author of Solid, thinks of it.
Re: Svelte: $derived can now be overwritten
#7[deleted]
Re: Svelte: $derived can now be overwritten
#8People who have migrated a large enough production codebase to Svelte 5, what's your devex like?
pretty good. some people in my team don’t like svelte magic and wish we were using react but others say, and i quote, “damn this is clean” or “almost effortless it just works” and i’ve seen again and again engineers ramp up pretty fast compared to my Knockout, Angular, or React times…
Pretty happy! Just wished they didn’t change their “magic” so often, but it’s the price to pay for innovation—if we can even call frontend development that, which I think we should but many frontend haters around here
Re: Svelte: $derived can now be overwritten
#9People who have migrated a large enough production codebase to Svelte 5, what's your devex like?
I'm almost finished with a large, complex app written with Svelte 5, web sockets and Threlte (Three JS) [0]. Previously, I'd written React for about a decade, mostly on the UI side of things.
I vastly prefer Svelte, because of how clean the code feels. There's only one component per file, and the syntax looks and writes deceptively like vanilla JS and HTML. There's a bit of mind-warp when you realize Svelte doesn't want you passing components with props as props into another component. Svelte gives you "Snippets" instead, which work for some reusability, but are limited. It sort of forces simplicity on you by design, which I like. Most of React's deep nesting and state management doesn't exist in Svelte and is replaced with simple, better primitives.
The bigger gain though for me was Svelte(kit) vs. Next JS. It's very clear what is on the server and what is on the client, and there's none of that "use client" garbage with silly magic exports for Next JS things. The docs are great.
Svelte's biggest disadvantage is that the UI library ecosystem isn't as large. For me that wasn't as big of an issue because it was my expertise, but everyone else looking for a drop in UI library will find the Svelte versions a little worse than their React counterparts.
Because svelte is compiled, it also is by default very snappy. I think choosing Svelte would likely give most devs a speed boost vs. the spinner soup that I've seen most React projects become. A lot of that is going to be in the skill of the programmer, but I love how fast my app is.
[0]: https://bsky.app/profile/davesnider.com/post/3lkvum6xtjs2e
Re: Svelte: $derived can now be overwritten
#10Agh, I understand why runes were implemented, but I still can't get myself to like them. It feels like Runes take away from what made Svelte Svelte (the simple, concise syntax), and changes like this seem like slow concessions back in that direction anyway.