nostr:nprofile1qyw8wumn8ghj7umpw3jkcmrfw3jju6r6wfjrzdpe9e3k7mf0qyf8wumn8ghj7mn0wd68yat99e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqgpxdq27pjfppharynrvhg6h8v2taeya5ssf49zkl9yyu5gxe4qg55huxsxu what ui framework are you using with your observables experimentation? I'm thinking of moving away from svelte. Is applesauce built around the observable/reactive paradigm?
Discussion
Having been very impressed by Svelte when I dabbled around with it a year ago I wonder what turned you away from it?
I have limited experience, but love svelte. Ha emt tried 5 yet though.
"Deep reactivity" means using proxies, which are a leaky abstraction. The way reactivity is handled based on component state is also leaky. And runes are magic which infect the rest of your codebase, making everything into compiled svelte code
What do you mean by “leaky”?
I made the switch to Next 14+ for all my apps a year ago. Tons of benefits.
what’s wrong with react?
I'm using react and I wrote my own small useObservable hook that lets components subscribe to the value of an rxjs observable
https://github.com/hzrd149/applesauce/blob/master/packages/react/src/hooks/use-observable.ts
I don't know if svelte has native support for observable, but Im sure you could write a really simple helper method that would allow components to use them. ( want to build a applesauce-svelte package 😉 )
Applesauce is broken into a few parts but the core of it is a large collection of helper methods https://hzrd149.github.io/applesauce/typedoc/modules/applesauce_core.Helpers.html and the in-memory EventStore https://hzrd149.github.io/applesauce/overview/events.html
The EventStore ( and QueryStore ) are designed to store all the events the UI layer needs and they expose a bunch of different observable methods that let components subscribe to events ( timelines, lists, profiles, zaps, replies, etc )
