I rather like the experience of working with Remix. Though it has some quirks. `remix-auth` is OK. `drizzle` works ok. I dunno, it depends on a lot of factors but in the spirit of your question this is what I'll answer.
Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
11–20 of 57 posts
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#12Svelte would be my vote. I don't like all the hoops Sveltekit is jumping through. I just want to compile ahead of time and get a bunch of dumb static files I can host somewhere. It's sad watching them move away from that.
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#13None. I just use react and express. Does everything I need. I don't use ORMs, I write my queries in sql files. Deployment I use github actions or jenkins.
The problem with writing raw queries is that you don’t get that sweet sweet type checking
Wrapper functions with typed parameters :)
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#14At $dayjob right now I'm using remix+supabase (although the supabase part is going away, but we're keeping postgrest). I have to say I quite enjoy it. DevEx seems good (although we've added quite a bit of our own logic on top). Performance is too early for me to tell. For my personal stuff I tend to do more app-like things, so SSR/SSG is not that useful to me, and I tend to go with pure react+redux. But I might try svelte when the new version comes out, it solves a lot of my issues with it.
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#15I would recommend - https://create.t3.gg/
It uses the following, which as of late are pretty well know and common, so you can punch in your problems to stackoverflow, google, or chatgpt and get some pretty good answers.
It uses:
Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM for sql and mongo)
Though of course these could go out of fashion tomorrow, but I don't think the essential idea behind these libs and frameworks are that wacky, unique or unordinary.
Prisma ORM, is a little opinionated, and you could swap it out for Drizzle, which is basically typescript side sugared SQL.
TRPC might be also be a little sticky because it is tied to typescript, this is the tradeoff for the buttery smooth coupling for the fullstack experience. I think there exists a typed-rest solution out there, but haven't used it.
Personal anecdata, I used this stack for a little hobby project and it was FUN.
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#16Svelte would be my vote. I don't like all the hoops Sveltekit is jumping through. I just want to compile ahead of time and get a bunch of dumb static files I can host somewhere. It's sad watching them move away from that.
Svelte is still there, and Kit is there for fullstack applications.
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#17I would recommend - https://create.t3.gg/ It uses the following, which as of late are pretty well know and common, so you can punch in your problems to stackoverflow, google, or chatgpt and get some pretty good answers. It uses: Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM for sql and mongo) Though of course these could go out of fashion tomorrow, but I don't think the essential…
Isn’t trpc redundant now that next’s server actions are out?
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#18[dead]
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#19None. I just use react and express. Does everything I need. I don't use ORMs, I write my queries in sql files. Deployment I use github actions or jenkins.
The problem with writing raw queries is that you don’t get that sweet sweet type checking
This. I can’t live without Prisma anymore.
Re: Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?
#20I like nextjs deployed on vercel but am not a big fan with the new direction of next so open to other frameworks. The other libraries I tend to change up depending on use case or what I want to try out. (this is mostly for basic crud/LLM wrapper apps)
> not a big fan with the new direction of next
Care to elaborate?