Phillippe

6 ms·

1.
by Phillippe 2y ago
The current Svelte version does it at build/compile time. The up and coming Svelte 5 is using signals and the reactivity is moved to runtime
2.
Pelte: Putting Svelte back into Svelte 5(pelte.dev)
2 points by Phillippe 3y ago|0 comments
3.
My thoughts on Svelte 5 as a full-time Svelte Developer for 3 years(poxi.substack.com)
3 points by Phillippe 3y ago|0 comments
4.
by Phillippe 3y ago
I don't mean to be rude, I'm just brainstorming. I'm sure they have thought about it I'm just commenting in the small chance that they haven't
5.
by Phillippe 3y ago
Maybe reuse the $:{} here, tho that would probably be really confusing for svelte 4 developers lol $:{ let name = 'world'; }; vs let name = $state('world'); $: is valid javascript right? So that should also work in .js
6.
by Phillippe 3y ago
I love all the changes except that single thing with let count = $state(0); I'm just brainstorming here, but what about an optional $reactive rune where everything in that is reactive by default? $reactive(() => { let name = &#
7.
by Phillippe 3y ago
"...isn't quite right — it would break _all_ your existing code that wasn't in .svelte files." What if it is opt-out reactivity in .svelte files and opt-in reactivity in .ts/.js files? Yeah I know it would be a bit
8.
by Phillippe 4y ago
It is very interesting to hear! Thank you for this writeup. I don't think it will be a problem tho, to all the people I've shown it to, like 5-6 people have absolutely loved the name, you're the first person who did not like
9.
by Phillippe 4y ago
Hey, I'm the creator Poxi (I'm not OP). Was just wondering what you mean by this? What is wrong with Poxi?