Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would you use?

I would recommend to not use a framework at all. I usually maintain legacy projects and modernize them for my clients. Whatever you feel is the latest shiny thing will be the legacy horror of tomorrow.<p>If I’m free to decide the tech stack it is HTMX with a backend technology that suits the business case. For web related work I usually choose Node.js and fastify without template engine. It’s fast and easy going.

None. I&#x27;d use Go with standard library templates and plain ol&#x27; CSS with a sprinkle of JS.<p>If I was forbidden to use that, I&#x27;d probably use Ruby on Rails, Django or something like that.

PHP &#x2F; Symfony.<p>It has Auth, Templating, ORM, Email, Caching, Forms, Validations.<p>For frontend I like Bootstrap or Tailwind as a base, but for interactivity I use a combination of htmx and Alpine.js, so everything&#x27;s pretty light-weight.<p>In the frontend world, I started reducing my reliance on it. I started quite a while ago and had went through jQuery, jQuery UI, bower, gulp, grunt, AngularJS, then the completely rewritten Angular 2+, Vue.js, npm, yarn 1, yarn 2, yarn 3, webpack, rollup, Parcel.js (which I like)...<p>It was too much for me to keep up. So I stuck with Symfony and try to keep the frontend light-weight.

I’d say use a “real” full stack (or batteries included) framework such as Laravel, Rails or Django. If you do need to use React, Vue, etc, then glue them with Inertia.js which is just a super thin layer that basically just replaces those frameworks templates by a modern js franework. Best of both worlds in my opinion, and a super stable and maintainable stack.<p>My problem with the ones you are mentioning (next, remix, svelte kit, etc) is that 1) they are not a full solution… you still have to figure out everything else, from authentication, authorization, sending emails, ORM, background jobs, etc… and 2) they’re in constant shuffle and rewrites and change of opinions so maintaining long running projects on these frameworks quickly becomes a nightmare.<p>If it’s for learning or a side project, then pick whatever. If it’s for business, pick tried and true and something g you’re confident in 2 years will be still maintained and not be a totally different beast (ehem, next).

None. I just use react and express. Does everything I need. I don&#x27;t use ORMs, I write my queries in sql files. Deployment I use github actions or jenkins.

I 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&#x2F;LLM wrapper apps)

I&#x27;d use <a href="https:&#x2F;&#x2F;leptos.dev" rel="nofollow">https:&#x2F;&#x2F;leptos.dev</a> because you can use a fully typed language (Rust) that is super fast in the backend and also in the frontend (see <a href="https:&#x2F;&#x2F;krausest.github.io&#x2F;js-framework-benchmark&#x2F;2024&#x2F;table_chrome_121.0.6167.85.html" rel="nofollow">https:&#x2F;&#x2F;krausest.github.io&#x2F;js-framework-benchmark&#x2F;2024&#x2F;table...</a>)

I prefer using Next. I&#x27;ve been using Remix at the day-job for about a year now. It&#x27;s fine, but I still choose to use Next with all personal work. I&#x27;d also prefer to work with it professionally. My personal dev-blog started in v12, I upgraded it to v13 a while back (not much involved in that upgrade), and at this moment am refactoring it to v14. A lot has changed, and for the better.<p>It provides a great solution for most needs and problems. But I think the biggest selling point is that their docs are excellent. I never connected with the Remix docs...they often left me still confused. I&#x27;ve used Remix v1 and updated our two work repos to v2. I still don&#x27;t feel fluent with it for some reason and often find myself thinking &quot;I prefer the way Next does this&quot;.<p>Someone else here mentioned the T3 stack. That&#x27;s a good resource to at least see other libraries&#x2F;services that work well with Next. You don&#x27;t need to follow any of it blindly, but use it as an information resource.

VueJS - syntax is very simple, you can start using it by importing it in &lt;script&gt; tag, or you can set up a full dev environment with vite, you can use vue dev tools plugin in chrome. It also has a very simple state management system as well as an event bus, if you want to go that route. and for backend - fastapi. i never found those &quot;all-on-one full stack&quot; frameworks to be usable.

Svelte would be my vote. I don&#x27;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&#x27;s sad watching them move away from that.

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&#x27;ll answer.

At $dayjob right now I&#x27;m using remix+supabase (although the supabase part is going away, but we&#x27;re keeping postgrest). I have to say I quite enjoy it. DevEx seems good (although we&#x27;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&#x2F;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.

NextJS is pretty good. Here’s why I’d recommend it:<p>- It’s so much easier to manage file-based routing. 1 new page == 1 new file.<p>- Super flexible about client&#x2F;server-side code on each page<p>- It’s concise, and easy to understand. The amount of code in a hello-world project is tiny, but scales up to large apps really nicely<p>- Easy to share things between client and server, typescript enforces type checking between client&#x2F;server too<p>- It’s mature, has a huge community and backed by Vercel.<p>Some cons… I hope you like JavaScript

Phoenix, and by extension elixir, are so nice to work with I could hardly consider using anything else.

Elixir + Phoenix (+ Svelte via live_svelte if you need very very real time stuff). Has everything you need and none of the BS that is the JS ecosystem. :)

I would recommend - <a href="https:&#x2F;&#x2F;create.t3.gg&#x2F;" rel="nofollow">https:&#x2F;&#x2F;create.t3.gg&#x2F;</a><p>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.<p>It uses:<p>Nextjs (React), typescript, trpc (typescript rpc), auth, tailwind, and Prisma (ORM for sql and mongo)<p>Though of course these could go out of fashion tomorrow, but I don&#x27;t think the essential idea behind these libs and frameworks are that wacky, unique or unordinary.<p>Prisma ORM, is a little opinionated, and you could swap it out for Drizzle, which is basically typescript side sugared SQL.<p>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&#x27;t used it.<p>Personal anecdata, I used this stack for a little hobby project and it was FUN.

I&#x27;m using Astro for a personal project and couldn&#x27;t be happier.<p>It&#x27;s not exactly the same as next&#x2F;remix&#x2F;kit, but does most of the same stuff and is a delight to work with. I love Svelte as well but SvelteKit, not so much

Remix. It ties together a lot of things that make sense.<p>The loaders and actions for loading and updating data just makes sense. Server side rendering just makes sense.

I use vite. It lets me work on pure React.js with Typescript.<p>Next.js, Remix, Astro, and Svelte are another layer of abstraction i dont want to deal with.

<a href="https:&#x2F;&#x2F;primatejs.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;primatejs.com&#x2F;</a>

Currently using SvelteKit for a project, and I dig it. I&#x27;ve used Vue in the past and tried to get on the React train, but both felt a bridge too far from good ol&#x27; HTML, JS and CSS. Granted, I&#x27;m mostly using the packaging and reactivity in SvelteKit - most of my server side code is written in Node using Express to better separate concerns, with some existing in SvelteKit mainly for BFF purposes.<p>I feel like if, down the road, I decided to ditch a framework altogether, writing it in Svelte may help seeing as there are very,. very few framework specific elements in it. I may also be deluding myself.

Express + Vue<p>wanna try Astro though

Supabase + SvelteKit = SupaKit

React&#x2F;Relay front end. Postgraphile&#x2F;Fastify backend. Postgres database. Typescript. The most OP type safe stack. One change in your database propagates throughout your stack.