Thoughts on Svelte(Kit), one year and 3B requests later

Post by _Tev » Wed, Jun 28, 2023, 2:43 PM UTC

pie_flavor wrote: post #173

NorwegianDude wrote: post #75

Earlier quoted context omitted.

I have tried to use sveltekit once and turned around in 20 minutes as routing is severely limited. All I wanted to do was to route based on domain, with a different set of routes for one of the domains. Not exactly complicated or uncommon, but not something you can do with the sveltekit router.

This is gone over in the github threads about such a feature - basically, as two different projects semantically, the best thing is to create two different projects physically, in a monorepo. All the code-sharing with none of the additional complexity.

So you cannot do dynamically named routes in svelte (e.g. localization)?

Just curious, I have no experience in svelte. It does sound like a major limitation.

Post by cxr » Sun, Jul 02, 2023, 5:58 PM UTC

sametmax wrote: post #43

I like the fact minimalist approaches, like svelte, htmx and alpine.js are getting more and more traction. I felt like fighting this fight alone for years in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did 10 years ago in a tenth of the time and code. So far I also survived: - xml is the future - let's use no…

> in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did

What if I told you jQuery was itself a "crazy stack"?

Re: Thoughts on Svelte(Kit), one year and 3B requests later

Re: Thoughts on Svelte(Kit), one year and 3B requests later