Rendered at 23:36:57 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
division_by_0 11 hours ago [-]
Looks good. Will def migrate my current project before publishing it.
A detail I find interesting:
> version.pollInterval now defaults to one hour, meaning SvelteKit will periodically check for new deployments and set updated.current to true accordingly. Previously, no polling occurred by default. [0]
I always use this in my projects combined with updated.check() when the doc becomes visible, but some people will probably not read this and see unexpected requests in prod.
I love Svelte and SvelteKit. But I keep going back to the batteries-included Django simply for the ORM, the admin backend and authentication packages. Nothing in the JS ecosystem comes close to it in terms of simplicity and integration-level and using third party modules always feels hacky and they pull in a thousand other dependencies.
I wish SvelteKit would become batteries-included, but that's not the direction they have in mind -- which is totally fair. It makes me sad nonetheless.
rich_harris 10 hours ago [-]
We definitely do want to move in that direction!
For now, we have add-ons for stuff like drizzle and better-auth (https://svelte.dev/docs/cli/overview) which makes it relatively easy to set up these things without committing the framework itself to a particular set of choices. But I totally agree that a lot of the time it's nicer to just not have to think about it. Our current focus is on laying foundations (async Svelte, remote functions, custom renderers etc) but it's very much on our medium term radar.
7bit 8 hours ago [-]
I was not aware! That makes me happy!
0xblinq 10 hours ago [-]
> Nothing in the JS ecosystem comes close to it in terms of simplicity and integration-level
Adonisjs has existed for more than 10 years. I’ve used Django for many years and I find Adonis way better (and ages more modern) than Django.
A detail I find interesting:
> version.pollInterval now defaults to one hour, meaning SvelteKit will periodically check for new deployments and set updated.current to true accordingly. Previously, no polling occurred by default. [0]
I always use this in my projects combined with updated.check() when the doc becomes visible, but some people will probably not read this and see unexpected requests in prod.
[0] https://next.svelte.dev/docs/kit/migrating-to-sveltekit-3#Co...
I wish SvelteKit would become batteries-included, but that's not the direction they have in mind -- which is totally fair. It makes me sad nonetheless.
For now, we have add-ons for stuff like drizzle and better-auth (https://svelte.dev/docs/cli/overview) which makes it relatively easy to set up these things without committing the framework itself to a particular set of choices. But I totally agree that a lot of the time it's nicer to just not have to think about it. Our current focus is on laying foundations (async Svelte, remote functions, custom renderers etc) but it's very much on our medium term radar.
Adonisjs has existed for more than 10 years. I’ve used Django for many years and I find Adonis way better (and ages more modern) than Django.