[RamblingCTO]

Yeah, I did a project in sveltekit + go and then one in htmx, alpinejs + golang. Sveltekit is quite big and not low maintenance.

Not sure what exact use case sveltekit would be good for, that can't be solved with htmx + alpinejs.

[michaelcampbell]

> Not sure what exact use case sveltekit would be good for, that can't be solved with htmx + alpinejs.

I mean, reductio ad absurdum:

    s/sveltekit/<anything>/; s/htmx + alpinejs/assembly/;

Of all of pg's writings, the one with "the blub paradox" in it has proven to me to be the one I see crop up again and again.

[devbent]

Svelte by itself is super tiny.

Sveltekit does a lot more stuff and is accordingly bigger.

[biomcgary]

htmx, alpinejs + golang is the exact stack I've been thinking about. I'm not a front-end developer, but want to be able to prototype things quickly. Are you aware of any public examples of this stack that go beyond "Hello, World!"?

[RamblingCTO]

I'm not actually, but I found it very easy to learn. The documentation really is enough. Htmx is used for requests and replacing content. You just need to figure out when to replace what. Alpine is used for on-site interactions. You can hit me up on twitter if you have questions, love to help other people with that stack! https://twitter.com/andinfinity_eu