[HN Gopher] Ask HN: Which full stack framework (NextJS, Remix, S...
___________________________________________________________________
Ask HN: Which full stack framework (NextJS, Remix, SvelteKit) would
you use?
And why? (Please do not answer with the usual "Use what you have
most experience with" or "It depends on the use case") Also what
libraries/services do you prefer to use in combination? For
example: -Auth -ORM/Db connector -Email -Deployment
(VPS/Container...)
Author : denismenace
Score : 9 points
Date : 2024-02-13 21:23 UTC (1 hours ago)
| root_axis wrote:
| None. 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.
| thatxliner wrote:
| The problem with writing raw queries is that you don't get that
| sweet sweet type checking
| root_axis wrote:
| Wrapper functions with typed parameters :)
| ed_mercer wrote:
| This. I can't live without Prisma anymore.
| joegibbs wrote:
| I do like Prisma, but I find that for quite a few queries
| it's ridiculously inefficient - things like getting counts,
| or where you have to get 20 of some model with a bunch of
| relations - that I find myself using a lot of queryRaw
| calls. Apparently this is because it doesn't use joins at
| all, it's all done sequentially. For some of the stuff
| where I'm getting counts grouped by month it goes down from
| 20+ seconds to under 200ms using raw SQL.
| mortallywounded wrote:
| None. I'd use Go with standard library templates and plain ol'
| CSS with a sprinkle of JS.
|
| If I was forbidden to use that, I'd probably use Ruby on Rails,
| Django or something like that.
| dian2023 wrote:
| 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/LLM wrapper apps)
| ed_mercer wrote:
| > not a big fan with the new direction of next
|
| Care to elaborate?
| aosaigh wrote:
| Not the OP but agree with their comment. For me, since Next
| 13 it's been a mess. The transition to the app router has
| been incredibly complex with lots of undocumented edge cases
| and other issues. Rendering in general has become very
| confusing with server-side, client-side and everything in
| between. There's also no real guidelines/structure for
| handling remote content, requiring projects like ContentLayer
| (which may actually be discontinued).
| devdude1337 wrote:
| 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.
|
| 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.
| builder555 wrote:
| VueJS - syntax is very simple, you can start using it by
| importing it in <script> 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 "all-on-one full stack" frameworks
| to be usable.
| dylanhassinger wrote:
| Express + Vue
|
| wanna try Astro though
| thatxliner wrote:
| Supabase + SvelteKit = SupaKit
| ThalesX wrote:
| 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.
| coreyog wrote:
| Svelte 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.
| fruktmix wrote:
| Svelte is still there, and Kit is there for fullstack
| applications.
| shirogane86x wrote:
| At $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.
| robbyiq999 wrote:
| I 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.
| ed_mercer wrote:
| Isn't trpc redundant now that next's server actions are out?
| slowtec wrote:
| I'd use https://leptos.dev because you can use a fully typed
| language (Rust) that is super fast in the backend and also in the
| frontend (see https://krausest.github.io/js-framework-
| benchmark/2024/table...)
___________________________________________________________________
(page generated 2024-02-13 23:01 UTC)