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.
Ask HN: If you were to build a web app today what tech stack would you choose?
61–70 of 214 posts
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#62Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#63Choosing a stack has always been a balance between "what you are currently productive in" and "the best possible tool for the job."
These days, assuming you have a base level of skill and experience, it's like 2-10x easier to get up to speed in a brand new stack thanks to those AI coding buddies
Your current competencies still matter and always will, but today, IMO we're way more free to choose the "best" tool and assume that we can get up to speed quickly.
Putting that aside, I still think Rails is amazing for "most" webby stuff. Would consider Flask if I needed things from the Python ecosystem. Or I guess Phoenix if I needed that massive concurrency. Would pair them with Postgres and/or Redis as needed.
For frontend... Vue? Or maybe just server-side rendering if I could get away with it.
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#64Literally anything, thanks to ChatGPT/CoPilot/etc. Choosing a stack has always been a balance between "what you are currently productive in" and "the best possible tool for the job." These days, assuming you have a base level of skill and experience, it's like 2-10x easier to get up to speed in a brand new stack thanks to those AI coding buddies Your current competencies still matter and always will, but today, IMO w…
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#65Just 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…
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 is a tiny API in Go that sends a JSON response and renders a static HTML page.
With my total lack of Web experience (and self-confessed hate of webapps as a user), I have no opinions on React, Rails, Node.js, Vue and whatever people are naming here. But I'm taken aback at the variety - there's 20-odd replies all giving different answers.
Does Web development in 2023 not have 2-3 tech stacks that dominate? Are the existing frameworks/techs so lacking that new ones keep appearing to address those problems? Is there a high rate of change because things keep improving? If so, where is that improvement for me as a user, when webapps still feel inferior to late 90s native programs?
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#66Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#67Just 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…
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#68- infra on AWS via AWS CDK TypeScript
- backend domain plain TypeScript
- frontend plain React, no framework (TSX)
- database RDS Aurora serverless v2 (Postgres)
- monorepo using pnpm
Re: Ask HN: If you were to build a web app today what tech stack would you choose?
#69But I believe that, in the early days, Drupal made excellent foundational design choices as a framework, and if you used it's APIs in your custom module development, then, generally speaking, you would have a secure website.
But now, D7 is approaching EOL, and I absolutely don't want to migrate to the latest flavor. D7 has been rock solid for a decade, and I have no desire to chase the latest fad.
I wish that there were a stable, monolithic solution that is simpler to setup (as in including everything, including database, webserver, SSL certs, etc.) that just worked and was extendable and overridable programmatically, in the same way that Drupal was.
Modern web stacks have become a bucket of Lego pieces that seems ok if you are an expert in everything and know how to put everything together exactly. The problem is, most people aren't experts in form handling, login and authentication, media handling, caching, etc.