I've published the 2nd part on this post, covering my front-end stack here: https://news.ycombinator.com/item?id=39919574

I'm interested in checking out Go.

Could you recommend a stack please? * Testing - test runner, mocking * Database - Typesafe queries, ideally as little abstraction as possible, migrations * Web app framework * Dependency injections (or do you prefer doing it manually over using a library)

Why Remix over Next?

As for the ORM / query building, did you also consider Drizzle and Kysely against Zapatos?

Next is buggy, Remix mostly just works, and I have zero interest in Vercel which is the Next selling point IMO.

I haven't played with either Drizzle or Kysely, looking at the docs Drizzle in particular looks slimmer and more sql-like which is a plus, though in general I think having an environment like dbeaver or data grip that gives you completions for your queries and developing them there then copy/pasting the code and getting type safety on raw queries with zapatos is still superior for power users who know sql.

A true background job would be impossible with this stack. Because I was on the Pro plan, in theory I could set the serverless function timeout to 900s.

Thanks Dave! That's a great summary of my experience.

Most of my experience has been with a more "boring" stack, so I was interested in trying some of the more "hyped" technology choices, to see if I was missing out on anything.

Yeah, makes sense.

I’m also in a phase where I get to start a lot of new low-stakes web projects, so I’ve made a point of adopting at least one new-to-me tool for each. I love typescript, and am generally happy with modern front-end tooling, but the node back-end ecosystem drives me bonkers — too many paper-cuts from too many tools along the lines you’ve documented here — and has me regularly retreating back to Python or Ruby land.

What Supabase functionality are you using? Database, Auth, etc.

What has your experience been like with them?

I agree, the context is important here. My use-case was B2B SaaS.

I'm interested it HTMX, but for a project like this I couldn't afford to lose out on React's ecosystem of pre-made components where the goal was to ship a professional looking SaaS web-app quickly.

Yes, exactly hashed and salted by bcrypt.

If I wanted harden this setup, my next consideration would be either having a separate microservice that's purely responsible for auth, or using 3rd party provider like Cognito.

My bias was always to err on the side of popularity. I thought that I would be less likely to encounter frustrating bugs and edge cases using choices that have been battle tested for a least a few years.

What I overlooked is that while the platform might be popular and mostly trustworthy (such as Vercel), there are specific solutions like the Vercel Cron Job are still relatively new (released Feb 2023) and still not ready for serious use.