Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

SvelteKit 1.0

svelte.dev

Post reply on HN
Print view View original

281–290 of 296 posts

Re: SvelteKit 1.0

#281

Post by Kuinox »

dmitriid wrote: post #280
Kuinox wrote: post #279

Earlier quoted context omitted.

> Web Containers which... aren't a standard The implementation doesn't use chrome specific API AFAIK, and it works on firefox. > are very specifically Chrome-only. And it undoubtedly relies on a bunch of Chrome-only non-standards, too. It does support all majors browers, except safari. The reason why it doesn't work on Safari is even listed: > Safari recently shipped support for SharedArrayBuffer and cross-origin iso…

I stand corrected. The reason for my comment is that far too often these complaints are about some things that Chrome ships at neck-breaking speed.

The standards do adds features too fast for the other browsers to catch up, that's true.

Re: SvelteKit 1.0

#282

Post by Existenceblinks »

akmittal wrote: post #260
crucialfelix wrote: post #191

Earlier quoted context omitted.

79.46 kb which includes React. That's never where the bloat comes from.

How so, that 80 kb is bloat

I believe that's already a compressed size (not minified) that means 200kB+ minified (zero app code).

Re: SvelteKit 1.0

#283

Post by sixbrx »

MentallyRetired wrote: post #200
yencabulator wrote: post #166

Earlier quoted context omitted.

The src/routes/posts/[slug]/+page.svelte thing is pretty recent, it used to be just src/routes/posts/[slug].svelte. I'm not exactly thrilled with the new naming...

I left the framework for this reason. When I asked about it, I was told "this is what Next will be doing soon". I need more reasoning than that, and it was indicative of the decision making process. Turned me off. Aside from that, Svelte is SUPER fast and easy to use. I may give it another go at some point.

More information about the reasons for the changes here:

"Fixing load, and tightening up SvelteKit's design before 1.0 #5748"

https://github.com/sveltejs/kit/discussions/5748

Re: SvelteKit 1.0

#284

Post by dmitriid »

Kuinox wrote: post #281
dmitriid wrote: post #280

Earlier quoted context omitted.

I stand corrected. The reason for my comment is that far too often these complaints are about some things that Chrome ships at neck-breaking speed.

The standards do adds features too fast for the other browsers to catch up, that's true.

It's worse than that, sadly. A lot of what is perceived as standards (that is they have an official sounding spec on w3c somewhere) are actually not, and are just Chrome releasing stuff.

If you go to MDN and click on multiple experimental APIs you'll find they do have a spec. And they are shipped in Chrome. And then you start reading the spec and it says "It is not a W3C Standard nor is it on the W3C Standards Track.": https://developer.mozilla.org/en-US/docs/Web/API

Re: SvelteKit 1.0

#285

Post by yencabulator »

solumunus wrote: post #267
MentallyRetired wrote: post #200

Earlier quoted context omitted.

I left the framework for this reason. When I asked about it, I was told "this is what Next will be doing soon". I need more reasoning than that, and it was indicative of the decision making process. Turned me off. Aside from that, Svelte is SUPER fast and easy to use. I may give it another go at some point.

I thought it was weird and couldn't see the reasoning, but personally I just persisted with using it and in the end I've found the new structure perfectly workable and perhaps even marginally prefer it. So yeh, it might seem stupid but maybe just try and use it more to find out if it's really that big of a problem for you. The rest of the gains I've had from SvelteKit were too good to pass up, it's overall just a sup…

Oh I'm still using SvelteKit. I just don't love having 3 or 4 +page.ts'es open in my editor.

Re: SvelteKit 1.0

#286

Post by reducesuffering »

culi wrote: post #98
jmull wrote: post #26

I'm just completing a job using svelte/kit, tailwind, postgres, typescript. Actually, I was new to the entire stack, but it went smooth as butter. (Though I have plenty of experience with JS, HTML, CSS, other databases, etc.) IMO, svelte and sveltekit are well designed and have a great dev experience. LOL, as I was writing this he was apologizing on the stream for the breaking changes. That was a bit of a pain, but n…

> My only real gripe is using folders to organize both layout hierarchy and route hierarchy is going to turn out to be a mistake. +1 to this. I think Next.js made this mistake too and is now backtracking

How is Next backtracking? Their v13 released with the app/ in beta doing exactly this Svelte/Remix style layout/route folder heirarchy?

app/page.tsx and app/path/page.tsx

Re: SvelteKit 1.0

#287

Post by wobedi »

Have been using svelte/sveltekit/sapper in production for two years now. Used React before and never looked back. Congrats on 1.0!

Re: SvelteKit 1.0

#288

Post by slimebot80 »

swyx wrote: post #75
yamrzou wrote: post #66

There is a plethora of javascript frameworks: React, Vue, Svelte, Remix, etc. If I know nothing about front-end development, and would like to learn one that is: - Intuitive - Suitable for small projects as well as large projects. - That is here to stay, i.e. either adopted by many companies, or its adoption curve is going up. Which one should I pick? Would Svelte be a good choice?

remix isnt like those others in that you’d also need React to do UI at this point React Vue and Svelte are all decent production choices, as for what is intuitive that really depends what YOU like, different strokes different folks svelte is probably the most fully integrated toolkit (animations, state mgmt, server side rendering, serverless api routes, etc) and ships the least javascript at this point tho if u want…

remix allows you to deliver zero JS :)

Re: SvelteKit 1.0

#289

Post by hu3 »

httgp wrote: post #232
hu3 wrote: post #27

This is how I move fast and break nothing. By having fullstack type-safety from database all the way to the frontend with auto-completion. My current stack: + SvelteKit (could be Next, Nuxt, Solid or any other TypeScript framework) + tRPC (typed calls between frontend and backend, https://trpc.io ) + trpc-sveltekit (glues SvelteKit and tRPC, https://github.com/icflorescu/trpc-sveltekit ) + Prisma (ORM, https://www.pr…

How well does tRPC work if the API consumer isn’t built with TypeScript?

I haven't used this, but check: https://github.com/jlalmes/trpc-openapi

Re: SvelteKit 1.0

#290

Post by foxandmouse »

jmull wrote: post #26

I'm just completing a job using svelte/kit, tailwind, postgres, typescript. Actually, I was new to the entire stack, but it went smooth as butter. (Though I have plenty of experience with JS, HTML, CSS, other databases, etc.) IMO, svelte and sveltekit are well designed and have a great dev experience. LOL, as I was writing this he was apologizing on the stream for the breaking changes. That was a bit of a pain, but n…

Did you just jump in with typescript without learning it first? how was that experience?
Post reply on HN