Live data from Hacker News

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

news.ycombinator.com

91–100 of 736 posts

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

#95

Django, in my previous role we did MVP websites for academics and the speed of getting a site up and running and deployed was just so fast. I’ve never worked with anything else that is as fast, anything like FastAPI or Flask or Express or similar either requires additional libraries to add really basic and common functionality or you have to roll it yourself. I personally don’t think that if you’re building an MVP yo…

This is where I came out a couple of years ago. I love Django and it has worked out perfectly. But I'm far from an expert.

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

#97
I'm currently approaching MVP / ready to pitch stage on something and these are my choices-

Rails 7.1 w/ Tailwind (esbuild, not import maps) Postgres DaisyUI for Tailwind UI components View Components for Ruby Nothing particularly "hot" but there are some newer tools

Post MVP, the only thing I'm looking to change is potentially replace a very heavy data analytic background job with a Crystal version of it. Will be super easy to port, and since I'm using Sidekiq, I'll drop in Sidekiq.cr and thus won't need to make any other system changes.

I'm thrilled about it, it's taken a month to go from zero to everything working and I'm just tidying up the marketing site

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

#99
Choose something from bucket 1 and pair it with an own-cloud PaaS such as what we're building at withcoherence.com! There's nothing that will help you move faster than using well-understood tools with huge ecosystems, and freeing yourself from glue code and internal tooling.

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

#100

Personally big on Rails (use it at work every day). But, my last MVP I did with TS/Next/Mantine/Supabase/Vercel. Reasons: - I've been using Rails as an API only, so having to grok views felt like a waste. My React skills made me feel that learning how to make complex views in my backend was a waste of time. - One type of bug I hate is ensuring my API calls have the right schema. With Supabase and TS in the frontend,…

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 app.

I also just really like react/JSX, very strongly typed coupling between the html and JavaScript. Makes it very easy to refactor and pull out new components with confidence.

I really think this is the best stack for an MVP CRUD app right now. Interested to hear of anything better.

Post reply on HN