3 ms·
FWIW, marko comes from Ebay. So, it scales - and being primarily SSR, its a better UX than your preferred frameworks
by nchmy 1y ago
FWIW, marko comes from Ebay. So, it scales - and being primarily SSR, its a better UX than your preferred frameworks
- afavour 1y agoPretty much every JS framework has SSR, the question is really how quickly does it hydrate. React typically rates poorly there but Svelte does great, at least partially because it has a compiler to optimize (like Marko does, it appears).
- nchmy 1y agoMarko did ssr by default, a decade before the other frameworks decided to bolt-on ssr...
- eyelidlessness 1y agoMarko’s compiler is designed for partial hydration (by default, without any special developer effort), which performs quite well. IIRC they were also looking at implementing “resumability” (term coined by Qwik, for an approach that sidesteps hydration as a concept entirely). I’m not sure where they’re at on that now, but I think it’s generally safe to say that Marko prioritizes load time performance more than nearly all other frameworks.
- mpeg 1y agomarko5 which is the stable version does partial hydration by default (like Astro, but with automatic boundaries) marko6 which is currently in public beta is resumable by default, and does some similar things to the also public beta qwik2
- hlimas 1y ago[dead]
- marginalia_nu 1y agoHTML rendering is, to be fair, not usually where you find the scaling issues.