For hosting I'll use Hetzner.
Ask HN: What would be your stack if you are building an MVP today?
151–160 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#152Re: Ask HN: What would be your stack if you are building an MVP today?
#153Postgres
React - createreactapp
Theres a few react frameworks I might sub out for now but otherwise this combo is a way to get things done right and quickly.
Re: Ask HN: What would be your stack if you are building an MVP today?
#154My priority is to get things done. Ubuntu (DigitalOcean VPS), Django, Postgres, HTMX. I'm going full old school boring tech. No excitement. No drama. I might even go typeless if the code is of reasonably manageable size.
Re: Ask HN: What would be your stack if you are building an MVP today?
#155I built Call Stacking ( https://callstacking.com/ ), a modern Ruby on Rails debugger, with Jumpstart Pro and 1.5 hours a night over the course of 4 months. We have four kids, host an exchange student, a new puppy. Our schedules are full . Nothing compares to the productivity of Ruby on Rails. Especially when coupled with a high-end template like Jumpstart Pro ( https://jumpstartrails.com/ ).
Re: Ask HN: What would be your stack if you are building an MVP today?
#156- Server: Node.js + SQLite I know JS very well, so writing HTTP handlers is quite fast. Node runs on V8, which is probably the fastest runtime for dynamic code. SQLite makes development easier as it’s just a file, gives you ACID. - Frontend: React/Mobx/Tailwind SPA hosted on firebase hosting. I think the concept of JSX (write your HTML with JS) is good as it gives you a real language instead of a restricted templatin…
I never got this reasoning. In Vue the idea is:
* Write html templates in HTML
* Call javascript from the template to do javascript things (i.e. computed properties and methods)
This has always made the most sense to me, conceptually.
Sure Vue gives you a DSL for looping template elements (v-for) or showing template elements (v-if), but almost all the typical javascript action happens inside typical javascript calls.
Re: Ask HN: What would be your stack if you are building an MVP today?
#157My priority is to get things done. Ubuntu (DigitalOcean VPS), Django, Postgres, HTMX. I'm going full old school boring tech. No excitement. No drama. I might even go typeless if the code is of reasonably manageable size.
Same but with Rails and traditional server rendering if it's feasible. I know React is becoming boring tech but imo it's just so much faster to bang out most of the boring pages server-side and then if you really need it, break out "cooler" client functionality into its own React sub-app.
Re: Ask HN: What would be your stack if you are building an MVP today?
#158Earlier quoted context omitted.
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…
Wish I could afford vercel
Re: Ask HN: What would be your stack if you are building an MVP today?
#159For something really minimal, an internal tool, I'd probably use grist. Grist is a "no code" spreadsheet program that is open source and works on a relational database. I just threw together an inventory management system for my weekly dnd group in a few minutes, and I've shared it with the group. I find the relational mindset grist uses a lot easier to reason about than traditional spreadsheets.
The next level up would be django with htmx. Very minimal javascript, I might embed a javascript "applet" like a map into it if needed. This covers 99% of data driven apps.
If I wanted to build something like say discord I'd probably use a pretty similar stack for the MVP, but with server-sent-events (htmx with server sent events is nice) and web components for more complicated interactions. That's probably why I'm not in charge for building complicated single page webapps with a lot of interdependent state though. I maintain this approach should work but haven't had a real chance to test it in the wild.
If I'm writing CAD software I'm probably going with QT/python/(numpy/jax/compute-shaders/sympy/etc). Python might not be the fastest, but when you're accelerating it with one of those machine learning libraries it can be really powerful. I've actually been working on something CAD-ish using that stack here: https://github.com/traverseda/PySdfScad
That's probably roughly the same stack I'd use for things like computer vision, machine learning, etc. Ironically anything where performance is important I'd probably choose python over a compiled language.
Mind you the QT python documentation is really not great, for a really minimal MVP I might swap qt out for pyimgui which is amazing for rapid prototyping but is going to be a real pain to do things like syntax highlight a text editor or embed HTML content.
Embedded electronics? Probably micropython on an ESP32 for an MVP. A REPL on your microcontroller is really nice. Robotics I'd probably use buildroot to build a custom linux distro. ROS is pretty heavy and I find it gets in the way a lot, but if you need ROS stuff obviously use ROS.
I don't have much experience with mobile development, so I'd probably end up using QT with python and pyqtdeploy, but that's not an approach I'd recommend anyone else follow. I'm keeping an eye on Tauri in that space, although I really wish they made it easier to bundle in things that aren't single page javascript web apps (like a python application).
So yeah, mostly I'd use python. Master of some trades, jack of a bunch of others, it's flexible and powerful enough that I feel happy to have specialized in it, even if deploying apps to end users can be finicky and annoying. I'd avoid the javascript ecosystem as much as possible, and where I'd have to use javascript I'd prefer to make self-contained web components.