Live data from Hacker News

Ask HN: What would be your stack if you are building an MVP today?

news.ycombinator.com

301–310 of 736 posts

Re: Ask HN: What would be your stack if you are building an MVP today?

#301
post #109
post #32

Earlier quoted context omitted.

I did so last year, and I cannot be happier. My only regret is that I wasn't aware of htmx/hotwire at the time. I went with Vue, and I regret it immensely. Rails is the fastest development platform I've tried so far, it is predictable, well crafted, structured yet flexible. You can't go wrong with it. Every now and then I try something new on a side project or I have to work on some other codebase for my customers, a…

IMHO, part of this is that people have accepted the poor experience of non-realtime applications. But there's a huge UX improvement if the application responds faster than users can input actions. Doesn't matter for all applications but if your users are going to spend significant time inputting data it makes a huge difference. Also IMHO, a flexible type system like Typescript makes development faster than without it…

> part of this is that people have accepted the poor experience of non-realtime applications

my experience has taught me the exact opposite: people have accepted the poor experience of real time applications (client side crashes that bring down the entire page, half-baked routing that is essentially just rebuilding the browser navigator, inconsistent client vs server rendering processes). developers tend to completely stick their head in the sand when these issues are occurring. there's complete classes of problems that simply go away when you're not building an SPA.

> Also IMHO, a flexible type system like Typescript makes development faster than without it. You can refactor faster

in the long run, yes, but in the short term you're probably not going to get your mvp out faster because you chose TS

Re: Ask HN: What would be your stack if you are building an MVP today?

#302

Earlier quoted context omitted.

It’s funny that only in our industry “time tested”/“battle tested” is called old school and frowned upon. No wonder we see software bloat everywhere.

Eh, I think experimental physicists and medical imaging also lean towards newer tech.

No area of health work tends towards new tech. It's disallowed by regulation.

Re: Ask HN: What would be your stack if you are building an MVP today?

#303
post #215

Hhere is quick survey : Regarding backend choices: curl "https://news.ycombinator.com/item?id=34530052" | grep -i Django | wc -l 36 curl "https://news.ycombinator.com/item?id=34530052" | grep -i supabase | wc -l 17 curl "https://news.ycombinator.com/item?id=34530052" | grep -i rails | wc -l 28 curl "https://news.ycombinator.com/item?id=34530052" | grep -i node | wc -l 15 curl "https://news.ycombinator.com/item?id=345…

tangent: asked ChatGPT to update your code to use for loops and voila: Backend Choices: for backend in "Django" "supabase" "rails" "node" "elixir" "phoenix" "fastapi"; do count=$(curl -s "https://news.ycombinator.com/item?id=34530052" | grep -i "$backend" | wc -l) echo "$backend: $count" done Frontend Choices: for frontend in "svelte" "React" "htmx"; do count=$(curl -s "https://news.ycombinator.com/item?id=34530052"…

Ask chatgpt to collect every possible frontend and backend frameworks form this post.

Re: Ask HN: What would be your stack if you are building an MVP today?

#304
Joystick [1] using MongoDB as the primary database. Run a few instances on VPS and then a load balancer in front. This is how I run my site [2] following a massive amount of headaches and random downtime fighting w/ a k8s cluster. Zero downtime since I moved it over in October. Only thing I don't like is I'm using a third-party DB host for Mongo (ScaleGrid) which has unfortunately gotten quite slow over the past year. Planning on moving this to a self-managed VPS as well.

[1] https://github.com/cheatcode/joystick

[2] https://cheatcode.co

Re: Ask HN: What would be your stack if you are building an MVP today?

#305
If you're building a B2B app:

- Supabase on the backend (REST APIs are a solved problem, no need to spend a single hour on it)

- Auth0 for authentication (too risky to manage authentication manually)

- react + react-admin SPA on the frontend (does 80% of the job for B2B apps)

- lambda functions (for business logic that can't be exposed on the frontend)

API-centric SPAs are such a time saver... when you don't have to build the API, and Supabase covers it.

For a B2C app, you must render server-side. I'd go with:

- Postgres - Next.js or Remix - Prisma

Re: Ask HN: What would be your stack if you are building an MVP today?

#308

Definitely old schools. I am building a MVP right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why. 1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want "fully built out" services, then we have a plethora of free and paid templ…

Is there a multitenancy package?

Is it this one?

https://djangopackages.org/grids/g/multi-tenancy/

I know there is a paid one.

Re: Ask HN: What would be your stack if you are building an MVP today?

#309

Definitely old schools. I am building a MVP right now(kinda building my parachute while jumping off the plane)and I went with Django. And here is why. 1. Very vibrant community of devs and time-tested open-source libraries.If you want a multi-tenancy there is a library for that. IF you want stripe integration there is one for that. If you want "fully built out" services, then we have a plethora of free and paid templ…

For context I'm someone who spent nearly 20 years doing almost exclusively python dev, attended the first DjangoCon in 2008, ran the Django community blog during its formation heyday back in the mid 2000's and built tons of Django modules, apps, sites etc, have commits on the Project from way-back, tech edited Django books, etc...

Did rails for a short while in 2010-2012 and absolutely hated it then spent 2012-2020 doing mostly Python/Flask dev for huge fintech companies on AWS.

I now use Javascript/React/Nextjs on Firebase/Google Cloud. So much less hassle, tons more libraries and what seems like an exponentially larger ecosystem. There's still weird shit with transpiling typescript to javascript etc... but overall I enjoy JS dev much more these days.

Re: Ask HN: What would be your stack if you are building an MVP today?

#310

Earlier quoted context omitted.

Same, Next.js, Vercel, Prisma, Supabase. I push to my GitHub repo and the site is live and deployed in less than a minute. With the stack you can use the same language, DTOs, libraries, etc.. both server and client side. Server side rendering ensures a graceful handoff between server rendered state and the resulting app state on the client. I’m also using MUI which includes all the components you need for a front end…

This stack is pretty incomplete for most MVPs, as unless you're building something trivial like a landing page, you'll probably at some point also need libraries or a custom implementation for: - Validations - Translations - Error and request logging and auditing - Security (CQRS, CORS, CSRF) - Permissions and a way to integrate it with your authentication (does supabase handle this? don't know) - Email sending - Bac…

(supabase CEO)

We wouldn't be the best fit for all of these, but here are some:

- Validations: handled already by Postgres and if you use JSONB you can use pg_jsonschema[0]

- Translations: probably won't ever be part of our stack, but for multilingual FTS we offer the pgroonga extension[1]

- Permissions: we offer AuthN (email & social logins, MFA, SSO) [2] and AuthZ with Postgres RLS[3]

- Background jobs: pg_cron [4]

- Caching: For images we have a smart cache [5]. We'll extend this to database queries over time

- File uploading: supabase storage [6]

[0] pg_jsonschema: https://supabase.com/blog/pg-jsonschema-a-postgres-extension...

[1] pgroonga: https://pgroonga.github.io/

[2] AuthN: https://supabase.com/docs/guides/auth/overview

[3] AuthZ with Postgres RLS: https://supabase.com/docs/guides/auth/row-level-security

[4] pg_cron: https://supabase.com/docs/guides/database/extensions/pgcron

[5] smart image cache: https://supabase.com/blog/storage-image-resizing-smart-cdn#s...

[6] supabase storage: https://supabase.com/storage

Post reply on HN