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

51–60 of 214 posts

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

#53
Two recent projects I wrote in C++20 using my own HTTP library. Only dependencies are a JSON library and a HTML template library (only used in one project). For these projects I used my own Postgres C++20 library.

Another recent project I did in mostly pure Java, with only a third-party library for SMTP email sending, and a library for using HTML templates.

IDE is VSCode with clangd as linter, and gcc as compiler, and CMake as build system. For Java, I use the RedHat VSCode plugin.

Frontend in pure TypeScript, with an icon library.

Challenges I encountered: - Statically checking data structures between frontend and backend. This needs code generation. And there was a lot of code repetition for shared data structures between front- and backend. - More database abstraction would be good.

Other than that it all runs great.

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

#54
Depends on project requirements of course and it's been a little while since I used them in anger, but sounds like Rails and Postgres are still going strong so I'd probably pick those. If something like React was strictly necessary I'd use React plus the most vanilla TypeScript stack, but I'd use only Rails' built-in stuff if at all possible. I don't know exactly about hosting but I'd probably go for something like Render or Heroku.

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

#56
post #16

LAMP. It can easily be maintained by a single developer. Scales well enough for a decent number of users. Huge ecosystem of components. Easy to deploy to literally any web host. Wide variety of front-end systems. If you need to scale, it can do that. Developers for it are plentiful. But you can always rewrite it in the flavour-of-the-month framework when you hit either scale or money.

For anything that is anticipated to grow beyond a very small codebase, the lack of static checkability really becomes a pain with PHP.

I'm surprised that Java and modern C++ are not more popular. I know for large web applications, Java is popular in "enterprise" environments.

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

#57
It would definitely either be TS or Python.

I think I might use Bootstrap but I'd heavily customize theming.

Probably SvelteKit or Vue for the frontend. Most likely SvelteKit.

SQLite or a flat file database for sure.

I think what I would do is use Tornado to serve SvelteKit pages, if I went with Python.

Definitely a monorepo for front and back end. Probably I'd try to do zero server side templating.

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

#58
post #16

LAMP. It can easily be maintained by a single developer. Scales well enough for a decent number of users. Huge ecosystem of components. Easy to deploy to literally any web host. Wide variety of front-end systems. If you need to scale, it can do that. Developers for it are plentiful. But you can always rewrite it in the flavour-of-the-month framework when you hit either scale or money.

Agree but with Postgres instead

FNPP

FreeBSD

Nginx

PostgreSQL

PHP/Python

Or, for something a bit less mainstream and only for certain types of application but more minimalist:

FNRL

FreeBSD

Nginx

Redis

Lua

Post reply on HN