4 ms·

Maybe just me but I actually think building web apps is already fun. I’ve got a hot reloading instant dev environment, I can publish to users in an instant… it’

Maybe just me but I actually think building web apps is already fun. I’ve got a hot reloading instant dev environment, I can publish to users in an instant… it’s great! Looking at the Marko examples I feel the same way I do whenever similar stuff gets showcased: it’s trying to focus too hard on brevity and/or cutesiness and doesn’t seem like it would scale well to a full, complex web app. But maybe it’s not supposed to and maybe that’s fine. React and Svelte and the rest can read clunkily at times but they have a clear separation of concerns and I’m glad for that.

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 ago
  Pretty 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 ago
    Marko did ssr by default, a decade before the other frameworks decided to bolt-on ssr...
  - eyelidlessness 1y ago
    Marko’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 ago
      marko5 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 ago
  HTML rendering is, to be fair, not usually where you find the scaling issues.
halapro 1y ago
React has a clear separation of concern? Excuse me? I only see do-it-all pre-styled components in the real world.

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 ago
Pretty 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 ago
  Marko did ssr by default, a decade before the other frameworks decided to bolt-on ssr...
- eyelidlessness 1y ago
  Marko’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 ago
    marko5 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 ago
HTML rendering is, to be fair, not usually where you find the scaling issues.

halapro 1y ago

React has a clear separation of concern? Excuse me? I only see do-it-all pre-styled components in the real world.