I'd run an API using Deno (https://deno.land), and consume that API with an SSR/SSG site built using Astro (https://astro.build). SCSS for styling, and probably just Vanilla JS (written in Typescript and compiled via Deno) — I increasingly find that unless my site is massively interactive, plain old Vanilla JS is totally sufficient.
Ask HN: What would be your stack if you are building an MVP today?
381–390 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#382Go & Postgres on the backend, running on a baremetal server. Because this is actually capable of handling a decent workload for really cheap compared to cloud. There's a few tricky bits to do with logs and reporting, but the benefits outweigh the pain. Vue on the frontend. Last time I used BootstrapVue and it worked well. I'd want to re-evaluate that decision next time, have a look at some of the newcomers. I'm aware…
This is the correct answer. It's quite shocking how many Django and Laravel answers there are in this thread. Performance and type safety appear to be completely irrelevant to HN. You should take a look at Vite ( https://vitejs.dev/ ) for a Vue development environment, if you haven't already.
thanks for the tip, I'll check it out :)
Re: Ask HN: What would be your stack if you are building an MVP today?
#383- Next.js frontend/backend, edgedb on top of postgresql, Linode server behind cloudflare. No Kubernetes.
Or, if you want to be more classical:
- kotlin backend using dropwizard, jdbi ORM connecting to postgresql. No kubernetes.
Or, if you want "plug and play" as backend:
- next.js, supported by postgREST. No kubernetes.
Or, if you want something exotic:
- elixir/erlang/phoenix as frontend and backend, no kubernetes.
I think the future is probably
- some frontend, edgedb, no kubernetes
Re: Ask HN: What would be your stack if you are building an MVP today?
#384I’ve gone all in on Cloudflare for my “stack”. R2, durable objects, D1, queues, logs, Pages and Workers. It all works beautifully, out the box, dev env baked in (wrangler), Internet scale.
Re: Ask HN: What would be your stack if you are building an MVP today?
#385Assuming web app.
1. Python.
2. Flask. Pure server-rendered HTML, no fancy frontend. Avoid JS as long as I can, just use jinja templates. If my app is not going to work with good old HTML and CSS chances are it's not going to work at all.
3. Classless CSS framework. I like this: https://watercss.kognise.dev/.
4. Sqlite3 or Postgres. Prefer postgres because with docker it's 5 minutes to set up. I use SQLAlchemy from the start because it makes life easier. If you ever deploy and worry about real data you add alembic for migrations.
5. One docker compose for everything.
6. Cheap VPS for like $3 per month.
That's it. I would like to upgrade my MVP stack, but it's battle-tested and it works well. After the 9 to 5 I only have like 3 brain cells alive so I need to get stuff done as fast as possible, which means using what I know.
One thing I often reinvent and reimplement is OAuth. Definitely "Sign in with google" is the best way to add auth to your app, but it's such a pain to set up.
Re: Ask HN: What would be your stack if you are building an MVP today?
#386Google Cloud Run or some similar scalable container-based abstraction. Off the shelf auth and DBaaS.
I have a lot of opinions on frontend stack too but they vary based on product.
Re: Ask HN: What would be your stack if you are building an MVP today?
#387For the database, anything that's managed - I'm partial to SQL server just based on my work history, but Postgres is nice too. Even the expensive ones are like $100/mo for the lowest production tiers, if you're bootstrapping with a W2 job that's reasonable for 6 months while you try to find some level of traction. For the backend, probably default to JS or maybe TS lambdas/function apps. Quick to write, quick to depl…
This sounds ideal to me. Are there any tutorials or resources that can help me use this stack? Thanks.
Re: Ask HN: What would be your stack if you are building an MVP today?
#388Hhere 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…
Should include Laravel too, which would also be my answer.
Laravel is just as big as Django and Rails in adoption, definitely should be included
Re: Ask HN: What would be your stack if you are building an MVP today?
#389Svelte + Typescript & Tailwind, .NET 7, SQLite. Why? Mainly because I'm familiar with them, and would be most productive with these. I'd almost like to reach for Blazor, but if it's at all public-facing, I don't think I can justify using Blazor at this time.
>I'd almost like to reach for Blazor, but if it's at all public-facing, I don't think I can justify using Blazor at this time. What are your concerns with Blazor for public facing apps?
Try navigating to the site for the Blazor material design library, MudBlazor, on a mobile browser:
As much as I want Blazor to work out well, those load times are too abysmal for me to seriously consider Blazor outside of internal apps.
Re: Ask HN: What would be your stack if you are building an MVP today?
#390Django. It can run anywhere, including in lambdas, and I prefer having a solid piece of back-end that won’t crumble when I start changing data models.