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

111–120 of 296 posts

Re: SvelteKit 1.0

#111

Post by samtp »

hedgehog wrote: post #92
samtp wrote: post #69

Earlier quoted context omitted.

I always wonder why Hacker News is such a magnet for comments trashing product announcements while also knowing almost nothing about the product being announced.

In the long run the approach Svelte takes seems very promising so I've kept an eye on it for a while now. I took umbrage at the snooty messaging towards a browser in a tool pitched as a way to "build production-grade websites".

Sure but the "snooty messaging" you're commenting on is from their tutorial, which is used to conveniently learn the framework in the browser.

This has nothing to do with Sveltekit itself. You can download a demo repo, enter "npm run dev" and see that it works on Safari without any issues. Hell, I've deployed ecommerce sites using Sveltekit used by 500k people/month where 60% of visitors are on mobile Safari without any issues.

So when a product is posted that you are unfamiliar with, maybe try giving it more that 30 seconds of consideration before dismissing it due to something completely unrelated to the product itself.

Re: SvelteKit 1.0

#112

Post by jherdman »

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…

I'd love to hear about your testing story with Prisma. I recently looked into it but was disappointed to see the recommended approach was more or less to nuke the contents of the DB (https://www.prisma.io/docs/guides/testing/integration-testin...) instead of just rolling back a named transaction at the end of a test (a la https://hexdocs.pm/ecto_sql/Ecto.Adapters.SQL.Sandbox.html, or just about every other framework I've used with Ruby or Elixir).

Re: SvelteKit 1.0

#113

Post by jakub_jo »

5e92cb50239222b wrote: post #91
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…

Same, but with ASP.NET (which produces an OpenAPI specification) + Entity Framework on the server, React + TypeScript on the client (which consume that specification through openapi-generator). https://github.com/OpenAPITools/openapi-generator I chuckle every time I read claims about Go (or whatever) being amazingly productive. I don't think it's possible to beat this stack with regards to both productivity and ease…

That sounds impressive.

Re: SvelteKit 1.0

#114

Post by marmada »

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…

I wonder if with Next.JS server components, we can just get rid of tRPC + trpc-sveltekit.

Re: SvelteKit 1.0

#116

Post by jdthedisciple »

swyx wrote: post #3

congrats team! the livestream and meta discussions around the launch are happening here https://www.youtube.com/watch?v=N4BRVkQVoMc theres a full in browser tutorial as well: https://learn.svelte.dev/ I've been keeping a reference implementation of a SvelteKit blog, inspired by @leerob's nextjs site: https://github.com/sw-yx/swyxkit/ for the past year and it's now updated for 1.0. hope it helps someone get going!

I checked out the blog and it doesn't seem to be rendering the Markup correctly.

For example the h2 headers appear literally as '## HEADER' on the website.

Re: SvelteKit 1.0

#117

Post by Tade0 »

As someone who wrote his first lines of JS in 2001, working with Svelte feels a lot like the good old days of JS when front-end was simple.

To me the main selling point is that the stack trace is actually useful for a change - you especially can find in there the line which caused the re-render and subsequent error.

JS frameworks/libraries by and large lost that feature a decade ago.

Re: SvelteKit 1.0

#118

Post by throwaway39048 »

capableweb wrote: post #107
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…

> This is how I move fast and break nothing Absolutely impressive how you are one of the first to find a approach that leads to a 100% bug-free development methodology. Or, you still have bugs right, so sometimes things break? Maybe you meant something like: This is how I move fast and don't have a certain section of bugs anymore ?

I bet they don't even move "fast" since that's relative and we haven't determined any baseline paramters. Very misleading. The comment should be "This is how I move (metaphorically speaking, not physically e.g. increased typing speed) with what I perceive to be faster than alternative stacks that I have explored and that doesn't have a certain section of bugs anymore".

Re: SvelteKit 1.0

#119

Post by deepsun »

jmull wrote: post #68
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…

Personally, I'd remove tRPC on down (and choose a database). It's nice there's type-safety between layers, but that's a bunch of layers that you don't even need. (A layer that doesn't exist takes is 100% type-safe and takes 0 hours to develop and maintain).

In Mongo you don't need to manage a schema, because it's SCHEMALESS! /s

Re: SvelteKit 1.0

#120

Post by swyx »

jdthedisciple wrote: post #116
swyx wrote: post #3

congrats team! the livestream and meta discussions around the launch are happening here https://www.youtube.com/watch?v=N4BRVkQVoMc theres a full in browser tutorial as well: https://learn.svelte.dev/ I've been keeping a reference implementation of a SvelteKit blog, inspired by @leerob's nextjs site: https://github.com/sw-yx/swyxkit/ for the past year and it's now updated for 1.0. hope it helps someone get going!

I checked out the blog and it doesn't seem to be rendering the Markup correctly. For example the h2 headers appear literally as '## HEADER' on the website.

that is a stylistic choice on purpose - i actually add the #'s in with CSS - just makes headers stand out a little more :)

i use h2, h3, and h4 often and just using font size alone makes it hard to tell which level of nesting the content is intended

you can see this on my main blog https://www.swyx.io/

Post reply on HN