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

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

news.ycombinator.com

Post reply on HN
Print view View original

451–460 of 736 posts

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

#452

Post by rubylark »

Thaxll wrote: post #126

There is only one good answer to that, you should use what you already know, if you build an MVP it's to deliver a product, it's not meant to spend 2-3x more time to learn new tech.

I'll add an anecdote to contradict that argument:

I work in embedded, and the place I work restructured to have a dedicated software group. They hired young software engineers and focused on getting people who are good programmers without really caring what they were good at. Most people ended up being web developers and liked webstack.

We were tasked with making a handheld air quality measurement device with a touch screen that could pair with a computer app that we would also write. Most people on the team knew webstack so we decided on a HTML/CSS/JavaScript +SQLite that would run in Electron Chromium on Linux on the physical device.

So what went wrong? Well, electron is bloated for embedded devices and the mid-tier processor we were using chugged so much that it would get hot. Hot enough to affect the temperature sensors at the top of the board and throw off the gas density measurements. Our MVP was nearly done when we discovered this problem.

We had two choices: throw out the hardware or throw out the software. We ended up throwing out the software and starting over (in Winforms + C# if anyone's curious). I and two others quit as a result. It is _really_ depressing redoing something you've already done in a different language.

If we picked the lighter weight framework from the start instead of picking the language most people knew, we wouldn't have lost a year of work.

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

#453

Post by adius »

Frontend: Elm + Tailwind, Backend: Haskell (or some instant API Generator like Postgrest / Airsequel), Database: SQLite, Automation: n8n / Pipedream / Zapier / …

The strong typing of purely functional languages makes refactoring a breeze and let’s you quickly iterate and move from prototype to production.

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

#454

Post by weaksauce »

treis wrote: post #109
lta wrote: 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…

with hotwire you get the benefit of having that SPA with quick responsiveness but with the much, much reduced complexity in stack with all the jankiness that that brings with it.

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

#456

Post by speakfreely »

quicksnap wrote: post #450

About a year ago I took off maybe 5 months to create a ephemeral voice messaging mobile app (Android + iOS) Stack: - React Native + Expo - Typescript - Supabase - Vercel - Some Vercel/nextJS-ish lamda functions so I could avoid AWS (Supabase didn't have that kind of offering yet) For me, it was _very_ pleasant to work in. I was able to ship features via OTA updates from idea to live in literally minutes.. sometimes e…

How did you define your models and manage database migrations with Supabase?

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

#457

Post by speakfreely »

squidsoup wrote: post #378
clint wrote: post #309

Earlier quoted context omitted.

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 d…

As a long time python dev, I’m now not certain why I would use python for a web app, over typescript on Next, other than familiarity. Sharing types between the server and client, and only having to manage _one_ software ecosystem is great.

What to you use for ORM/database migrations with Next.js apps?

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

#458

Post by spapas82 »

1. Rhel 9 (alma/rocky linux) on a vps (don't really matters where, aws, azure, do, hetzner, wherever).

2. Postgres 15

3. Python 3.10/Django 4.x served with gunicorn

4. Jquery and or alpine js

5. Bootstrap 5

6. Caddy to serve everything

7. S3 if a lot of file uploads are needed

--

I'd definitely keep using the same stack post mvp by vertically scaling the db, horizontally scaling the app servers.

Post reply on HN