3 ms·

Hi Nick, just saw your svelte summit presentation you gave and was pretty impressed with Edler.js! I have a simple site, basically 5 different templates. 2 of

Hi Nick, just saw your svelte summit presentation you gave and was pretty impressed with Edler.js! I have a simple site, basically 5 different templates. 2 of those templates will be used for content of ~500 pages each. So Elder was exactly what I was looking for. However: I want to re-hydrate my server-side rendered app/dynamic-parts including client-side routing. Elderguide (and in the YT talk) mentions that for more complex SPA-y stuff I shouldn't use it. I played around with Elder but finally settled on Routify, because it gives me re-hydrated client-site routing out of the box. SvelteKit I haven't looked into at all because they released it just when I was done with my app ;-) Would you mind elaborate how Elder's feature differ from SvelteKit? Thank you! PS.: Even if my use-case might isn't a fit, I think the use-case's where Elder would be my first choice are pretty clear.

nickreese 5y ago
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 https://github.com/Elderjs/elderjs/pull/130

nickreese 5y ago

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 https://github.com/Elderjs/elderjs/pull/130