Ask HN: If you were to build a web app today what tech stack would you choose?

Post by lgkk » Mon, Oct 30, 2023, 1:08 PM UTC

cookiengineer wrote: post #158

lgkk wrote: post #154

I’d use whatever scales best for the least cost. Go backend. Single binary. Big performance. I’d use Go for as many things as possible until I actually had a need for distinct technologies (queues, redis, etc.). Throw embedded db into the mix and you shouldn’t have any problems for a long time. React UI on cloudflare pages. Free. Easy. Postgres. Single node goes far. Great plug n play extensions. Same as with Go I ca…

Do you by any chance know whether there's something like a go library or converter/transpiler that allows you to reuse the structs from a backend on the client side? Currently I always have a little redundancy in my projects when it comes to the JS HTTP client that calls the golang backend's API and I want to avoid that.

Post by throwaway167 » Mon, Oct 30, 2023, 1:39 PM UTC

Post by [deleted] » Mon, Oct 30, 2023, 2:03 PM UTC

stephane-klein wrote: post #162

I just started a project and chose this stack: - SSR SvelteKit with Hydration ( https://github.com/sveltejs/kit ) - PostgreSQL database server - Postgres.js - PostgreSQL client for Node.js ( https://github.com/porsager/postgres ) - Migration powered by graphile-migrate ( https://github.com/graphile/migrate ) - PostgreSQL Row-Level Security ( https://www.postgresql.org/docs/16/ddl-rowsecurity.html ) - svelte-headlessu…

Post by hknmtt » Mon, Oct 30, 2023, 2:13 PM UTC

Post by codegeek » Mon, Oct 30, 2023, 4:46 PM UTC

martinald wrote: post #48

.NET 8 for the backend, and then blazor webassembly for the front end if it's complicated, or just boring old server side rendering with htmx if it's not. I've seen a lot of projects fail/struggle in golang (package ecosystem is still missing a lot of basics imo) or nextjs (very buggy). .NET has been my secret weapon. It's boring, works really well, has a good ecosystem and asp.net is really well thought through and…