To be honest, I've only briefly played with SvelteKit as it still isn't finalized.
Here are the main parts where Elder.js stands out
pros:
* Purpose built for large sites with SEO in mind.
* Hooks and plugin ecosystem for common issues. Responsive images, sitemaps, critical path css, etc.
* 0kb JS and partial hydration.
* Blazing fast builds.
* Async shortcodes make working with and future proofing static content a breeze.
cons:
* The complex Rollup implementation needed for partial hydration leads to less optimal dev experience. HMR isn't a possibility as it currently stands. Until `esbuild` is stable reloads won't be as fast as with Vite.
* Unfamiliar way of handling routing / no dynamic routing. (PR to simplify this is basically done [0])
* No client side routing.
* Less optimal for "apps" and logged in experiences until this PR is merged. [0] This should happen in the next week.
---
[0] https://github.com/Elderjs/elderjs/pull/130