Ok, I think I'm all in on CSS view transitions. The new stack: MPA + view transitions + web components + island architecture w message bus No complex state management. This is going to simplify app dev by an order of magnitude.
@gordon.bsky.social Do you have links to the "island architecture w message bus" approach? :o
@gordon.bsky.social Oh cool I do a similar approach for Agregore actually. But instead of components listening on window I wire them up in a main "script.js" so I can keep the components separate from the data and general app shape. https://github.com/AgregoreWeb/agregore-browser/blob/master/app/ui/script.js
Got any code I could read?
I've come to believe there are basically two good architectures for apps: - Elm App Architecture: strict tree of state machines - Message bus: no direct parent-child relationships, everything connected via messages over one bus
...Tradeoff between determinism and complexity. EAP is deterministic but state management is complex. MB is simple but not as deterministic. Both have great debugging properties. And if you can break the app into smaller bits, then I think simplicity of msg bus may win.
@gordon.bsky.social Linux desktop uses the message bus approach FWIW :o https://en.wikipedia.org/wiki/D-Bus
@gordon.bsky.social this is very similar to what ive done with web components, although i have used a combination of an incoming message bus from the serverside and tagging components with ids of other components they might want to directly interact with. it works well :> death to complex frontends!
It's just something that I've been playing with... Simplest version: - Components emit custom events for requests like "toggle sidebar" - Sidebar component listens on window for bubbled "toggle sidebar" events. Components don't need to know about each other, they just pub/sub custom events.