Live data from Hacker News

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

news.ycombinator.com

421–430 of 736 posts

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

#421

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…

Did a big migration from Flask to Django for my main side project for all of these reasons earlier this year. I love Django. It's criminally underrated. Side project if anyone's interested in peeping it: https://www.fpgajobs.com

Fellow EE here and love what you do! Loved your post on scraping.Btw, I thought you used Flask. Looks like I was wrong.

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

#422
A web3 stack, everything client-side and peer-to-peer. HTML/CSS/JS for front-end. JS/blockchain for backend. JS client-side storage/compute, JS libp2p library for peer-to-peer discovery, networking, syncing, updates, user-generated content, etc. Blockchain for things that need to be tamper-proof or involve payment.

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

#423
- for edge functions cloudflare workers are currently the best mix of being modern and professional/feature rich

- nothing beats the simplicity and power of svelte for UI

- netflix falcor for state and request management, because it has the 90% of features of graphQL i need but is much simpler to reason about and i can auto generate nearly all my requests from svelte without writing queries (because falcors model matches 1:1 to POJOs and has optional schemas so prototype at lighting speed and then add schemas later as needed for reliability)

- pouchdb/couchdb because nothing beats this combination for sync and offline and low latency features

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

#424
I'm currently building an mvp using Supabase & Next.js (FE & api routes). I can definitely recommend.

My main reason is speed; you can move very fast, and lots of the "boilerplate" stuff is handled out of the box.

I do keep post MVP in mind, it should be pretty easy to move parts to different systems if necessary. The most radical exit would be moving the Postgres DB elsewhere, or even self hosting Supabase.

It's good that it's possible, but I plan to use this stack as long as possible as it's great, and I have zero interest in managing and maintaining infrastructure.

As with everything; it depends. On your product and on your skills/expertise.

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

#426

Earlier quoted context omitted.

The biggest benefit to Django, in my opinion, is the orm and admin tooling. Being able to fix things in your app without having to open a repl or open a database tool is absolutely killer.

I honestly cannot believe that Rails doesn't have this built in. This was something that was in Django for as long as I can remember; I was looking at it in I think 2006 and it existed at that point in a very similar state to what I've seen lately. Not a dig on Rails, like "Oh, Rails is so bad they don't even have..."; rather, Rails is extremely capable, and so are Rails devs, so I legitimately don't understand why t…

Rails has Active Admin which is equivalent to what you get with Django. It's just not a core Rails gem but it's one line in your Gemfile to add it.

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

#427

Well that depends a bit on what the MVP needs to be. Anything web related I'm probably going the Elixir/Phoenix route. I'm no web dev, but this combination makes me actually kind of like doing web-things with how batteries included it is, and the tools it provides to really jump start a project. Then I'd host it "old schoolish" in a VPS or similar since that's what I know best. Might consider being fancy and investig…

Totally agree! For almost all web-based MVPs the PETAL Stack (Phoenix with LiveView & TailwindCSS) deployed to FREE Fly.io is an epic choice for both response times, realtime features, dev speed (time to market). We're currently building our MVP with it and it's fully Open Source so anyone can learn from our journey: https://github.com/dwyl/mvp

I really wanted to like LiveView but starting from 0 in the Erlang world meant learning a whole bunch of language semantics and idioms.

In fact I found it perhaps harder to get started than learning Rust, especially because the language server seemed unable to offer as rich completions compared to Rust.

In the end I did manage to understand most of the primitives and concepts in the basic sample app, but it did make me re-evaluate if it is the best choice in terms of technology adoption when it departs from most typical Python/JS/C family style conventions.

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

#428
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…

But doesn't that ignore the negative comments, e.g. don't use rails! /s

for that case we need to build a language model :D

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

#429
Front end: Is SEO relevant? YES: AWS Lambda generating server rendered HTML behind API Gateway. NO: Vanilla React.JS app hosted on S3

Back End: AWS Lambda behind API Gateway

Database: AWS DynamoDB

This stack will reduce down to zero usage costs when there is no traffic and will scale up to much more than I will possibly need for anything resembling an MVP with no interference required by me.

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

#430
Plain js on the frontend. Complex logic handled in rust-wasm. Backed handled in Rust using the Actix Web http server, using websockets, proxied through a very basic nginx instance with TLS.

My own servers for the entire cloud, maybe with CloudFlare as a CDN.

Avoid anything else as much as possible. If you need AI/ML, you're going to have to pull in some difficult extra stuff, so make sure the value is there.

Owing both to the unreasonableness of the modern javascript stack (node/eslint/jest/react/typescript/webpack) and also to the considerable improvement of vanilla js over the past 10 years, I really don't feel like all the extra frameworks are worth the overhead and dependency risk on the frontend. Vanilla js is really good these days! And when you need a boost, rust wasm is also really good.

I've found that it's a lot faster - and also a lot safer! - to build in vanilla js than I ever would have expected. Typescript still adds value, but imo not nearly enough value to earn a place in the stack.

Post reply on HN