‹ BackHN Continuity

Thread

SvelteKit 3

408 points · 179 comments · sampsn

  1. poetril · · focus · HN ↗
    After far too many hours using react, Svelte has become my favorite frontend framework. I’m seeing a lot of comments about how it stacks up in the LLM age. Prior to Opus 4.6-8 (and that era of model releases) they often struggled to get Svelte 4/5 code straight and mixed it up quite a bit.

    But having used it A LOT this year for personal projects, large work initiatives, and one-off web tools. I’m happy to say all the modern llms seem to do just fine with it. They even handle the experimental features, like remote functions, very well. It’s mostly preference but I find reading Svelte code much more pleasant than React/Vue.

    1. etatester · · focus · HN ↗
      Svelte changed things up at every single version so that's what you get. I've been a fan/hater since v1. For me Claude still tried to write "export let" for props even if I specify Svelte 5 at times.
      1. kevinak · · focus · HN ↗
        This just isn't true. It barely changed from 2019 when Svelte 3 was released until Svelte 5 at the end of 2024.
        1. etatester · · focus · HN ↗
          You're just forgetting.

          1-2 basically a different templating language

          2-3 basically a different templating language

          4-5 compatible but changed again

          That's 3 syntax changes over 4 versions.

          1. prophesi · · focus · HN ↗
            They explicitly mention that Svelte hasn't changed much since version 3? Svelte 5 did introduce runes but, as you say, still kept legacy code compatible.
          2. Sammi · · focus · HN ↗
            It really only got popular at version 3, so there's only been two syntaxes that most people have had to work with.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.