elderjs VS qwik

I like SvelteKit and am using it on projects, but this looked interesting too https://elderguide.com/tech/elderjs/

I'll just throw it out there though: it looks like Elder.js might be a another good option for this: https://elderguide.com/tech/elderjs/

If you're comfortable with html and not afraid of learning Javascript you should be able to pick up Svelte quite quickly. There's a cool project build on it called Elder.js and it's all about massive statically generated sites from data.

This lets you reduce your payloads while still having control over component lazy-loading, preloading, and eager-loading. While lesser known than Astro, Elder.js included partial hydration as early as August 2020, roughly six months before Astro's initial commit.

Personally for SSG I use Elder.js and found it to be great. Built both my hobby project and work project using it.

I mostly use Svelte (https//svelte.dev) for any frontend development, and stick with two frameworks: SvelteKit(https://kit.svelte.dev) or Elderjs (https://elderguide.com/tech/elderjs/).

Svelte might be worth looking into. There is even another version called ElderJS that boasts 10k+ paged SEO First deployments, both server side and static site. For reference, Elder.js easily generates a data intensive 18,000 page site in 8 minutes using a budget 4 core VM

If you're dead set on SPA, I'd take a look at Elder.js. It's Svelte based and is designed to handle SPA prerendering at scale.

Lazy loading exists, although I don't know enough about the framework to know how it works: https://github.com/BuilderIO/qwik/blob/main/packages/docs/pages/guide/lazy-loading.mdx

If you made it this far, thanks for reading! Learn more about Qwik here, or follow us on Twitter to get updates as we have them

To put this idea into practice, we built Qwik, a framework that is designed around resumabilty and achieves excellent startup performance. We're also excited to hear from you! Let's keep the conversations going and get better as a community at building faster web applications for our users.

This is neat! I’m curious if you see this being extended for other languages, or the concept being applied in other projects?

As for similar concepts, several projects by builder.io have some overlap. Most notably Mitosis[1], but I’d be shocked if TS-Lite[2] isn’t using similar techniques. Potentially Qwik[3] as well but I’m not sure, I would have bet that’s using Mitosis but it looks like that’s the other way around.

1: https://github.com/BuilderIO/mitosis

2: https://github.com/BuilderIO/ts-lite/tree/main/packages/core

3: https://github.com/BuilderIO/qwik

If you have any questions, ask away on our discussions forum and join our Discord server.

Some projects that can help automate this for you include Qwik, Partytown, Marko, and Astro

Qwik is a unique JavaScript framework in that it is the only one that exists today that can hydrate out of order at a component level. It goes beyond that though Qwik introduces a new concept to the vernacular of JavaScript: The Resumable Framework.

Server-side JS is an exceedingly useful tool for certain use cases. Specifically, sharing server and client logic. I know everyone here likes to hate on JS frameworks, but the productivity of being able to build one thing in one language instead of the same thing twice in two languages is hard to overstate.

Sure, that has some trade offs like page bloat. But almost all of the JS framework universe is focused now on reducing or eliminating those trade offs: partial hydration, build time code elimination, server components, etc. There’s still a long way to go before the DX and UX reach parity, but it’s inevitable, and closer than one might think (see Qwik[1]).

1: https://github.com/BuilderIO/qwik