Live data from Hacker News

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

news.ycombinator.com

121–130 of 736 posts

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

#121
I know this is not really in the spirit of the question, as asked. But an important consideration after having spent countless hours over many years building “MVPs” that ultimately go nowhere.

Hire a PHP/LAMP dev for $10/hour or less (or whatever is cheap and good enough) + something like digital ocean. Communicate effectively the features and milestones and project manage but mainly Spend my time on growth

I’m at a point where I can’t fathom writing a ton of code myself when I am trying to start a business. Programming is a hobby that I enjoy, but my time as an entrepreneur is more valuable elsewhere. Most likely I’ll find the business’s largest hurdle earlier and, it’s probably not a technical one. Then I can decide if it’s something I want to pursue or pivot to something else.

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

#122

As somebody trying to learn the web stack, reading this thread makes me a little sick to my stomach. Edit: Thanks for the advice!

I've only recently come back to the world of web after doing mostly devops/backend stuff. While getting on the JS framework treadmill might get other people hired, staying server side + Bootstrap kept me sane and productive. The only place where I spent an innovation token[0] was on htmx and so far it's been absolutely worth it. [0]: https://boringtechnology.club

what backend do you use?

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

#123

As somebody trying to learn the web stack, reading this thread makes me a little sick to my stomach. Edit: Thanks for the advice!

Don't think about it too much. Most of the web still runs on plain old PHP and HTML. New technologies pop up every now and then but most people who do this professionally just want something that does the job and don't talk about "their stack" outside of work hours.

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

#124
Next.js for both backend (server React and REST API) and frontend. Prisma ORM to Planetscale DB (mysql auto scaling). NextAuth. TailwindCSS. Typescript.

Very simple, very easy to deploy and scale, and in-tune with all the best practices of fast frontend (auto caching, SSG, ISR, prefetching, client side nav, etc)

Didn’t like Django. Deployment more annoying, templates are weak and DSL-specific, React integration is poor and then DRF is a strange verbose monstrosity.

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

#128
MVP should be built on things you will use later. Which is C#/Java/Python, React, and Postgres SQL unless your product has unique needs outside of the traditional space (it's a game, ML project, IoT project, mobile-only app, etc).

Firebase is too expensive. Only use case if you have only front end devs.

Dynomo/Mongo/Cosmos all do the same niche thing - you don't need a no-SQL db for most apps.

4. Apparently a lot of YCombinator companies still use Rails. I don't really understand why.

edit: I didn't know about Supabase - thanks.

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

#129
I've gotten fast enough with Go + Twirp/proto for the API. sqlc+pgx for the database interface. (i.e. generate as much code as possible). I have a couple of functions/middlewares I can pull in for user auth. I don't think this is that much slower than Django if at all.
Post reply on HN