I was initially skeptical of Svelte, but I'm starting to warm up to it.
Putting all of the scripts, markup, and styles in the same file per-component makes a lot of sense, even if I'm not the biggest fan of some of the special syntax they use within Markup.
Next, I'm curious to learn more about the compilation process.
I really like it, though still very much a noob.
I was initially skeptical of Svelte, but I'm starting to warm up to it.
Putting all of the scripts, markup, and styles in the same file per-component makes a lot of sense, even if I'm not the biggest fan of some of the special syntax they use within Markup.
Next, I'm curious to learn more about the compilation process.
I've been using it lately to develop some nostr clients and I feel the same way. I'm still figuring out the best way to manage with more complex state.
Do your frontends handle all their own business logic, or do you use a separate controller or a BFF or the like?
I'm doing everything on the client side using CQRS and Event Sourcing, I have some command models that publish events and some read models (svelte stores) that build the current state by subscribing to events.
I used CQRS heavily in a past life. Powerful, but definitely over complicated a few areas of the product that didn't need the full event sourcing pattern treatment.
We're Svelte maxis at nostr:nprofile1qqsra2ey033mkdwl5w8q0jss9ak69zafh82xsuvhwsaauw3trkq2amgpz9mhxue69uhkummnw3ezuamfdejj7qg7waen5te0vask6etn9enkzmt9wf68ymmw9ehx2ap6xsurgwp0qyv8wumn8ghj7enfd36x2u3wdehhxarj9emkjmn99u247xz7 led by nostr:nprofile1qqsz52pcperj0srl30csqmmhd79yesv5r34uv3aamafgnly7uvwctwgpz9mhxue69uhkummnw3ezuamfdejj7hzhfep.
I have been a StencilJS maxi for a while, but perhaps I can add Svelte to the quiver.
I haven't used Svelte, but we built an app with Vue and the layout was very similar.
Not a bad way to organize your modules as long as your editor can handle the different types appropriately.
