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

121–130 of 214 posts

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

#121

Post by ydnaclementine »

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…

Web dev frameworks are like pizzas: everyone has their favorite toppings and styles, some are more popular than others, and others are sometimes loathed (pineapple), but it generally all comes down to cheese, dough, sauce at the end of the day.

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

#123

Post by filestorage »

Frontend: Angular or Vue, deployed on AWS S3 bucket + cloudfront (for https)

Backend: AWS Appsync (or AWS API Gateway) integrated with AWS Lambdas written in Golang. Authentication through AWS Cognito. DB: anything serverless from AWS (Dynamodb, Aurora etc.)

This way the app would be 100% serverless, no need for effort to scale it or to maintain the infrastructure (apart from automating the ifrastructure through AWS CDK).

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

#124

Post by yetanother12345 »

Exactly the same "tech stack" as I used before that term became popular:

    - HTML
    - JS (Ecma Script, not some "framework")
    - CSS (not "Typescript" or whatever, standard CSS)
For backend I'd use PHP. Yes, PHP.

Edit: The same would apply for $job

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

#125

Post by exabrial »

MichaelNolan wrote: post #71
exabrial wrote: post #46

For internet facing webapps where infinite customization of html/css is important: Jakarta EE: Java 17/CDI/Quarkus for the backend, HTMX for the frontend. Quarkus is now standards based and has a large community. Java executes at near CPP speed but with memory safety. Java has the literal best debugger in the industry and also the combination of CDI and Mockito make writing true unit tests easy and fast. It literally…

Are you sticking with java 17 for a specific reason instead of java 21/latest? Besides that I agree with everything you wrote, Java is an incredible ecosystem.

17 for the minute, although Tomcat already has support for virtual threads

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

#126

Post by pxeger1 »

yetanother12345 wrote: post #124

Exactly the same "tech stack" as I used before that term became popular: - HTML - JS (Ecma Script, not some "framework") - CSS (not "Typescript" or whatever, standard CSS) For backend I'd use PHP. Yes, PHP. Edit: The same would apply for $job

Typescript and CSS are orthogonal. I think you’ve misunderstood what typescript is, or had a brain fart / typo.

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

#127

Post by mattrighetti »

filestorage wrote: post #123

Frontend: Angular or Vue, deployed on AWS S3 bucket + cloudfront (for https) Backend: AWS Appsync (or AWS API Gateway) integrated with AWS Lambdas written in Golang. Authentication through AWS Cognito. DB: anything serverless from AWS (Dynamodb, Aurora etc.) This way the app would be 100% serverless, no need for effort to scale it or to maintain the infrastructure (apart from automating the ifrastructure through AWS…

You won’t need a lot of effort to scale even with a Go backend deployed on an EC2 instance in the majority of cases.

Serverless is cool when you start with 300 users and you’re still in the free tier plan. After that, it’s going to cost you a fortune when you really need to scale, and I’m not even thinking about the time that you would need to waste writing everything back to a monolith/microservice, because that is what’s going to happen most likely.

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

#129

Post by mattrighetti »

If it’s a personal project, I would pick and try out the latest trends that I’ve been keeping an eye on.

I’m planning to try out HTMX + a backend written either in Rust or Go. Since it’s a passion project it doesn’t necessarily need to be out there for thousands of users, so I’ll go with SQLite.

Post reply on HN