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

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

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 51 posts

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

#31

Post by thrwwycbr »

dinkleberg wrote: post #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…

I am currently learning golang and HTMX. Do you have maybe some good example projects that a newbie like me can take a look at, which implements best practices?

Any advice for potential pitfalls?

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

#32

Post by kaaaate »

Recently I re-wrote my personal homepage (which was previously written in Vue.js) and the homepage for my discord bot in PHP (w/ smarty, and some CSS copied from Bootstrap).

For one of my other projects, my discord bot dashboard (which uses MongoDB and lots of boilerplate stuff for interacting with MongoDB), I'm using ASP.NET Core and Boostrap. It does the job, and it does it quite well.

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

#33

Post by [deleted] »

m_km wrote: post #30
bbsz wrote: post #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 ba…

I don't understand the downvotes to this comment.

[deleted]

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

#35

Post by codingdave »

ralmidani wrote: post #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,…

What made your old Node code not work? I've picked up old node projects from up to 10 years ago and they all still work just fine, so I'm unclear what pain you encountered?

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

#36

Post by joshstrange »

Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at.

I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For Postgres I like Neon [1] though their recent pricing changes make it less appealing.

[0] https://sst.dev

[1] https://neon.tech

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

#37

Post by ralmidani »

codingdave wrote: post #35
ralmidani wrote: post #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,…

What made your old Node code not work? I've picked up old node projects from up to 10 years ago and they all still work just fine, so I'm unclear what pain you encountered?

If you use the same Node version and NPM dependencies it could work, but trying to get the project upgraded to use a modern version of Node and mitigate vulnerabilities was a nightmare and I just abandoned the effort.

I get emails from Github with long lists of vulnerabilities on old toy projects where literally __zero__ dependencies are listed in package.json. It’s not so much the vulnerabilities that bother me, but the dependency conflicts, and in general a massive amount of infrastructure I have to buy into without even knowing it.

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

#38

Post by switch007 »

joshstrange wrote: post #36

Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at. I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For…

How do you feel about $0 vs $20 for e.g. a VPS that just sits idle? Is the complexity of AWS worth it for $20/mo?

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

#39

Post by joshstrange »

switch007 wrote: post #38
joshstrange wrote: post #36

Most my personal and side-business projects have very spiky load or just low load in general. Because of that I love using AWS Lambda as my backend since it scales to 0 and scales to whatever you have your limits set at. I use SST [0] for my backend with NodeJS (TypeScript) and Vue (Quasar) for my frontend. For my database I use either Postgres or DynamoDB if the fit is right (Single Table Design is really neat). For…

How do you feel about $0 vs $20 for e.g. a VPS that just sits idle? Is the complexity of AWS worth it for $20/mo?

> Is the complexity of AWS worth it for $20/mo?

For some of my projects it is, for others it wouldn't matter but I like keeping my AWS skills sharp since I use them professionally as well. There have been many times that I've had a solution at my fingertips for my job because I had previously played around with something on AWS for a personal project. I see it as a sort of "continuing education".

I also just dislike managing servers, call me whatever you want for feeling that way but I'd rather spend my time writing code and not worrying as much about patching/upgrading my servers. I know there are downsides to using Lambda, I've hit almost all of them, but I still prefer it over managing a server.

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

#40

Post by ralmidani »

jmaker wrote: post #14

Yes it’s the echo chamber of the promotion funnels that makes it appear as if everyone were jumping ship every few days. In my bubble, Angular and React are the primary frontend frameworks, with Vue sometimes being ahead and sometimes behind either. Virtually no one uses Svelte in my circles., but most folks have heard of it or have applied it in their side projects. HTMX is even more niche, still up for discovery fo…

I doubt many advocates for htmx (or Hotwire) believe React is being abandoned right now. However, they do represent a serious challenge, because they’re not just marginally faster or more ergonomic like, say, Preact or Svelte - they represent a complete paradigm shift from how we’ve been building Web apps for the past ~decade. Being able to have over 80% of the interactivity you can get with React while expending perhaps 20% of the effort (no build step, no client-side data modeling and routing, no client-side state, easier for server-side oriented devs, use a language you’re already proficient in, reduced cognitive load, etc.) is huge.

Many pioneering technologies are initially met with skepticism. A decade or so ago, jQuery was the clearly dominant client-side library. Very early adopters of React and its siblings were swimming against the tide, but eventually they made jQuery much less relevant.

I’m not saying htmx will definitely become what React is today, but the belief that a dominant technology or paradigm is safe from disruption has been repeatedly proven wrong.

Post reply on HN