Migrate to svelte 5 xd
Btw I looked into it, hard to find sceptics of runes. Did you run into issues with serialization of proxies or were there 3rd party lib api compatibility problems?
What important use case did cause you dislike it?
Flotilla version 0.2.7 has arrived! This will hopefully solve some stability issues folks have been having — if problems persist, let me know!
Also in this release is the long-awaited "Calendar" tab. Now you can manage calendars within relay-based groups! Give the new release a try and let me know how it goes — new versions are available via nostr:nprofile1qy3hwumn8ghj7en9v4j8xtnwdaehgu3wvfskuep0dehhxarjdp5hxurpdehszgthwden5te0veex2etydakksatzxyh8yet9d3hx2arhdaexktn9w5hszxthwden5te0dp38ytnrdaexzcmvv5h8xmmrd9skctcpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgcwaehxw309ahxverz9ehx7umhdpjhyefwvdhk6tcqypuvuma2wgny8pegfej8hf5n3x2hxhkgcl2utfjhxlj4zv8sycc86dwkfwk, app.flotilla.social, and (eventually) Google Play.
Changelog:
* Add calendar events
* Migrate to svelte 5 (fixes some bugs, probably introduces others)
* Migrate to new welshman editor
* Make reply indicator nicer
* Make share indicator nicer
* Improve feed loading
* Show marker for last activity in chat
Migrate to svelte 5 xd
Btw I looked into it, hard to find sceptics of runes. Did you run into issues with serialization of proxies or were there 3rd party lib api compatibility problems?
What important use case did cause you dislike it?
The proxy stuff was one thing, all my events get copied when they get saved to indexeddb, but since you can't detect proxies (except by copying them), there's no way to fix it in once place except try/catch every put operation. On top of that, the`$state.serialize` thing has to happen in a`.svelte` file. But I don't want to infect all my normal code with svelte stuff, I like to keep the two separated.
Other things:
- Reactivity has subtly changed. Stores don't see to be enough in every case. I've had to wrap a store in a`$derived` to get reactivity working.
- Reactivity is much more magical. Stores are extremely simple, but there's no way to dig in and debug runes.
- Runes also work the same way as react hooks do, which means implicit state based on when the variables are accessed or modified. This breaks timeouts, async functions, etc, and leads to hacks like`untrack`
It's not horrible, it's just... worse