[d1sxeyes]

> the need for getters and setters when using $runes in functions; this is a waste of time and almost always unnecessary in the contexts in which one uses small store classes

Yes, but then you can just use a class.

> using folders for routing and using standard page.svelte.js and server.svelte.js naming for everything

This wasn’t introduced with Svelte 5, this is SvelteKit.

> Despite all this, Svelte 5 introduces $writable

No it doesn’t? Do you mean $state()?

[rxliuli]

> Yes, but then you can just use a class.

Yes, but I immediately pointed out the oddities of the combination of class and runes below, which looks very strange and inconsistent.

> Despite all this, Svelte 5 introduces $writable

I don't know what this is.

[d1sxeyes]

> I immediately pointed out the oddities of the combination of class and runes

True, and it is a bit weird, but you made it difficult to understand your point by talking about a function which creates and returns a class for some reason.

It took me a second to work out you were the author of the original article, rather than OP by the way, didn’t really understand properly for a moment.