Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

news.ycombinator.com

Post reply on HN
Print view View original

91–100 of 214 posts

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

#91

Post by brundolf »

The answer to this kind of question is always "whatever you're most comfortable/productive with"

For me personally, I've been working on one that's pretty app-y and used Postgres + Deno + React/MobX (built with esbuild)

I'm very comfortable and happy with TypeScript, so I like having it on both ends (especially because I can share types between the two sides of the wire). And Deno and esbuild make the tooling story really simple and no-nonsense on the back and the front respectively, while being less opinionated than a framework like Next (I like Next for other things, just didn't choose it here)

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

#92

Post by irq-1 »

ACS_Solver wrote: post #65
Zealotux wrote: post #23

Just had been thinking about this today, the current state of web development is making me seriously depressed. I would pick what I'm most comfortable with, a simple monolithic Nest.js application running Fastify, with Postgres or SQLite, Dockerized, hosted on a predictably-priced host like Hetzner, and Ansible to automate everything. I know that stack will give me plenty of headroom until I eventually need to scale…

The discussion is making me scared from another perspective. I have experience with a pretty wide variety of development. I've worked with embedded microcontrollers (minimalistic RTOS), embedded applications (on top of a proper Linux), desktop applications in Java and in C#, some C++ work, gamedev and more. But to this day I haven't touched Web apps. I have not written a line of JS and the closest I've done to modern…

My 2 cents: keep working with Go. Learn just enough about templates to start, JSON to struct mapping and URL routing. It's not a great backend, but the client is what you really need to learn. For the client look through browser tools F12. For the basics of HTML, CSS and JavaScript skim through https://www.w3schools.com/ [People HATE this site but it has very limited info, making it a quick read.] For actual documentation use MDN https://developer.mozilla.org/ and skip any framework/library until you have the basics.

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

#94

Post by andrewstuart »

chrisdalke wrote: post #5

This depends on your goal: Are you trying to build + finish a project, or learn a new skill? I like to separate these goals, or otherwise try to scope projects very narrowly. For the former, I tend to reach for the tech stack that I've spent years working in and can very quickly spin up projects in. This is heavily specific to your background, but for me: - Frontend: React, vite, react-router, Chakra UI. - Backend: N…

Exactly this, but I’d only deploy to a simple cloud virtual machine, and not from AWS, Azure or GCP…. 9 cents a gigabyte is crazy.

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

#95

Post by meiraleal »

Just pure ol' JavaScript with a couple libraries.

Frontend: Lit and Tailwind (in reality, unocss, a tailwind runtime that doesn't need build)

Database: indexeddb + some CRDT

Backend: no backend, webrtc to sync between devices without a central server

Hosting: Github and cloudflare cache, the app has a functionality to deploy itself, generating a minified tailwind CSS and if needed, a "SSR" version of it (but without hydration, this is the part of the frontend craziness that I don't wanna get close).

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

#96

Post by andrewstuart »

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…

Do you deploy .NET on Windows or Linux?

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

#97

Post by HuwFulcher »

j0hnyl wrote: post #90

The last few web apps I've built: Flask / HTMX / Pico.css / Postgres or Sqlite Dockerized so that it's easy to spin up. Edit: Caddy for webserver.

Interesting that you mention Pico. I really like it (my personal site uses it) but it doesn’t strike me as the go to choice for a web app?

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

#98

Post by SwiftyBug »

andrewstuart wrote: post #94
chrisdalke wrote: post #5

This depends on your goal: Are you trying to build + finish a project, or learn a new skill? I like to separate these goals, or otherwise try to scope projects very narrowly. For the former, I tend to reach for the tech stack that I've spent years working in and can very quickly spin up projects in. This is heavily specific to your background, but for me: - Frontend: React, vite, react-router, Chakra UI. - Backend: N…

Exactly this, but I’d only deploy to a simple cloud virtual machine, and not from AWS, Azure or GCP…. 9 cents a gigabyte is crazy.

What's a simple cloud virtual machine?

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

#99

Post by catlover76 »

Zealotux wrote: post #23

Just had been thinking about this today, the current state of web development is making me seriously depressed. I would pick what I'm most comfortable with, a simple monolithic Nest.js application running Fastify, with Postgres or SQLite, Dockerized, hosted on a predictably-priced host like Hetzner, and Ansible to automate everything. I know that stack will give me plenty of headroom until I eventually need to scale…

> edge, workers, cloud functions

Those are things people do not need unless at an appropriate scale, or appropriate use-case, etc.

Post reply on HN