Live data from Hacker News

Ask HN: What web development stack do you prefer in 2024?

news.ycombinator.com

1–10 of 51 posts

Ask HN: What web development stack do you prefer in 2024?

#1
Curious to hear what those starting new projects/startups are choosing for web application tooling and frameworks. This is meant to be an informal survey of the HN community for their web development preferences.

On the front end side of things, I feel that React is not the default framework as Svelte and HTMX are everywhere (or maybe I am reading too much Twitter). On the backend side, I think it is a bit more open and has to vary from project to project based on specific needs but would love to hear what you are using and why anyway.

For many, I realize the answer may be to use the tools you are most comfortable with but wanted to ask just to see.

Re: Ask HN: What web development stack do you prefer in 2024?

#5
I’m building out my server-side with Django while reading up on htmx. I haven’t started with actual UI interactions, but htmx is what I plan to use.

For more context, I’m essentially revisiting an app I built from 2015-2017, before I became employed in the industry. I built it with Django and Ember. Long story short, Django upgrades nicely, while anything requiring Node that was built that long ago is “lost in time, like tears in rain…”

Yes, I’m resentful. And yes, I hope I never have to touch Node/NPM again.

Some other great options are Elixir/Phoenix/LiveView (I used it at my most recent job, and loved it) and Ruby/Rails/Hotwire. Hotwire is not coupled tightly with Rails, but using it with Rails would be the path of least resistance.

Personally, I went back to Django for reasons including:

- Data modeling and migrations with Django’s ORM are top-notch.

- Auth and admin which come out of the box are key for getting to an MVP quickly.

- I find Django’s template language more intuitive and more elegant than erb and EEx/HEEx.

- Python is still king in the data world, so it’s easy to integrate with mature DS/ML/AI libraries.

- If I need to find talent, Python devs are everywhere.

Re: Ask HN: What web development stack do you prefer in 2024?

#7
Core vitals:

Vanilla JS

CSS

HTML

--------

Frameworks:

HTMX[0]

Tailwind CSS[1]

Cash[2]

--------

Backend:

PHP

NodeJS

--------

For quick mockups & landing pages:

Webflow[3]

Carrd[4]

--------

Also some no-code SaaS solutions for dealing with tricky stuff like forms

[0] https://htmx.org/

[1] https://tailwindcss.com/

[2] https://kenwheeler.github.io/cash/

[3] https://webflow.com/

[4] https://carrd.co/

Re: Ask HN: What web development stack do you prefer in 2024?

#8
I can provide somewhat unorthodox answer for 2024.

I am currently working on a solo project and EXTRA prioritizing for time to MVP. In the past I already delivered one project with React and I found it very unpleasant to debug with my backend even if surprisingly useful for handling complex dynamic behavior in UI. I decided that MVP might as well be as vanilla at it can get considering that I am building very much backend-data driven application.

Python + Flask for backend. vanilla HTML + vanilla Javascript for little of the dynamic behavior that I need now on frontend. after MVP I'll most likely transfer to React because there's a limit where it will become pointless to write JS scripts by hand.

Re: Ask HN: What web development stack do you prefer in 2024?

#10
I’m gonna be a hipster by saying I was using Htmx (and its predecessor intercooler) before it was cool. I really wouldn’t think of specifically using Htmx to build your app. You use server side template rendering and then you sprinkle htmx on top to make it a bit nicer.

My preferred stack is server rendered go. I’ve traditionally used pongo2 for templates since they are nicer than standard go templates imo. But I’ll be trying out templ on my next project.

But whether you use go, Django, rails, laravel, whatever, if you’re doing traditional server rendering rather than the SPA or modern “full stack” framework, you’ll have a better time. And this is coming from someone who actually likes using SPA frameworks for interactivity. But managing client and server side state is so much more complex.

Post reply on HN