5 ms·

Svelte & SvelteKit has been wonderfully productive for me. It's a bit insane that I have adopted it across so many projects of mine despite the fact it is pre 1

Svelte & SvelteKit has been wonderfully productive for me. It's a bit insane that I have adopted it across so many projects of mine despite the fact it is pre 1.0 (well that has more to do with me I guess), but I am just faster with it. I have used a lot of frontend frameworks over the years, and before SvelteKit Vue & Nuxt were what I was warming up to. The article really focused on measurable things like type checking and surveys (not sure exactly how much that's relevant to a single team), but if I tried to quantify: - Svelte/Kit is conceptually small - Svelte/Kit's diversions from common practice are disruptive at first but quite productive if you really let them sink in (ex. path based naming, +page.svelte/+page.server.ts/+server.ts) - Svelte's ability to run in various different modes (SSR/node/vercel/etc) is awesome At this point Vue3 & Nuxt3, Remix, etc have caught up in many ways but I really really love using Svelte/SvelteKit. I recommend trying it at least once.

zztop44 4y ago
Same. I normally prefer boring old tech, but I’ve migrated all my projects over to Sveltekit. Yep, breaking changes are annoying but it’s worth it. It’s got the point where you’d need to pay me lot to work on a Vue or (especially) React project.
- hardwaresofton 4y ago
  Yeah I look at it this way: - Angular introduces structure, people realize that Directives are awesome but dirty checking is bad. - React re-focused frontend on components (to be fair Backbone/Marionette and some MVVM stuff was going this way already but whatever), people realize they really mostly just want big hierarchies of components and to minimize everything else. The Flux data flow pattern is alluring too but kind of unnecessary. - Vue cloned react but improved on it by introducing the data object via automatic tracking and radically simpler APIs. I read up and was productive with Vue in like... 1 day of reading docs. - Svelte builds on all of that, moves more magic into the compiler and introduces weird syntax but thoroughly consistent ergonomics and lower complexity. - Everyone goes SSR For people who want jobs, React is still king and probably will be for a very very long time. But you can pry SvelteKit from my cold dead hands.
  - galaxyLogic 4y ago
    Plain JS -> Angular -> React -> Vue -> Svelte What a long strange trip it's been
    - hardwaresofton 4y ago
      Don't forget jQuery! :) It feels like it was Plain JS -> jQuuuuuuuuuuuuueeeeeeeeerry -> Angular -> React -> Vue -> Svelte
      - graftak 4y ago
        React is quite a bit older now than jquery was when react came out. The react reign is going on for longer than jquery has been.
      - galaxyLogic 4y ago
        Right I totally forgot about JQuery. That too
yawnxyz 4y ago
Yeah same. My convoluted Vue 2 and React projects are much smaller and easier organized / maintainable as rewritten in Svelte vs. Vue 2. Until Svelte and Kit becomes difficult, slow, or hard to use, I'll keep using it. No need to switch to another at this point. I'm even using Kit to build out simple REST API endpoints, it's so simple.
- hardwaresofton 4y ago
  > I'm even using Kit to build out simple REST API endpoints, it's so simple. YUP. SvelteKit is one of the things that made me throw out my 3 tier (3 repo) project boilerplate. I mean I always knew I was slowing myself down (I'd look out the window and see all the Rails kids frolicking wild and free, not a care in the world), but I just didn't feel like I could trust my API code to Nuxt for some reason. I don't know what it was. Nuxt 3 is much better since they explicitly call out API routes but... SvelteKit properly making space for API endpoints and being so light that I felt I could just pop a few endpoints in there and it absolutely broke that barrier for me. Now I quite often mix back and frontend, and even streaming endpoints are fine too (they added support for streaming responses).
dbrueck 4y ago
Ditto. It's my go-to for all new web projects - we just move so much quicker in it, and don't usually spend a whole lot of time thinking about it - most of the time, it just doesn't get in the way at all.
hardwaresofton 4y ago
Just noticed my formatting faux pas. Even after this many years on HN…

zztop44 4y ago

Same. I normally prefer boring old tech, but I’ve migrated all my projects over to Sveltekit. Yep, breaking changes are annoying but it’s worth it. It’s got the point where you’d need to pay me lot to work on a Vue or (especially) React project.

hardwaresofton 4y ago
Yeah I look at it this way: - Angular introduces structure, people realize that Directives are awesome but dirty checking is bad. - React re-focused frontend on components (to be fair Backbone/Marionette and some MVVM stuff was going this way already but whatever), people realize they really mostly just want big hierarchies of components and to minimize everything else. The Flux data flow pattern is alluring too but kind of unnecessary. - Vue cloned react but improved on it by introducing the data object via automatic tracking and radically simpler APIs. I read up and was productive with Vue in like... 1 day of reading docs. - Svelte builds on all of that, moves more magic into the compiler and introduces weird syntax but thoroughly consistent ergonomics and lower complexity. - Everyone goes SSR For people who want jobs, React is still king and probably will be for a very very long time. But you can pry SvelteKit from my cold dead hands.
- galaxyLogic 4y ago
  Plain JS -> Angular -> React -> Vue -> Svelte What a long strange trip it's been
  - hardwaresofton 4y ago
    Don't forget jQuery! :) It feels like it was Plain JS -> jQuuuuuuuuuuuuueeeeeeeeerry -> Angular -> React -> Vue -> Svelte
    - graftak 4y ago
      React is quite a bit older now than jquery was when react came out. The react reign is going on for longer than jquery has been.
    - galaxyLogic 4y ago
      Right I totally forgot about JQuery. That too

yawnxyz 4y ago

Yeah same. My convoluted Vue 2 and React projects are much smaller and easier organized / maintainable as rewritten in Svelte vs. Vue 2. Until Svelte and Kit becomes difficult, slow, or hard to use, I'll keep using it. No need to switch to another at this point. I'm even using Kit to build out simple REST API endpoints, it's so simple.

hardwaresofton 4y ago
> I'm even using Kit to build out simple REST API endpoints, it's so simple. YUP. SvelteKit is one of the things that made me throw out my 3 tier (3 repo) project boilerplate. I mean I always knew I was slowing myself down (I'd look out the window and see all the Rails kids frolicking wild and free, not a care in the world), but I just didn't feel like I could trust my API code to Nuxt for some reason. I don't know what it was. Nuxt 3 is much better since they explicitly call out API routes but... SvelteKit properly making space for API endpoints and being so light that I felt I could just pop a few endpoints in there and it absolutely broke that barrier for me. Now I quite often mix back and frontend, and even streaming endpoints are fine too (they added support for streaming responses).

dbrueck 4y ago

Ditto. It's my go-to for all new web projects - we just move so much quicker in it, and don't usually spend a whole lot of time thinking about it - most of the time, it just doesn't get in the way at all.

hardwaresofton 4y ago

Just noticed my formatting faux pas. Even after this many years on HN…