I am sticking to Typescript nowadays, its so easy to share types between FE and BE, creates monorepo with many different packages.
I am in fact building MVP right now with Nextjs and Nestjs, i've never felt more productive than this
Ask HN: What would be your stack if you are building an MVP today?
561–570 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#562Earlier 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…
This stack is pretty incomplete for most MVPs, as unless you're building something trivial like a landing page, you'll probably at some point also need libraries or a custom implementation for: - Validations - Translations - Error and request logging and auditing - Security (CQRS, CORS, CSRF) - Permissions and a way to integrate it with your authentication (does supabase handle this? don't know) - Email sending - Bac…
The post is literally about building an MVP. Remix isn't a minimalist framework - it's a full stack web framework.
Re: Ask HN: What would be your stack if you are building an MVP today?
#563Angular and Express. I'm familiar with it and it's easy to iterate fast with what you get out of the box.
Re: Ask HN: What would be your stack if you are building an MVP today?
#564If it's a proper MVP that needs code and can't be validated via concierge or other no-code approach:
- React Vite Typescript (React Query and Hooks*)
- Python Flask Backend
- SQLite or just fsyncing a JSON file to disk on each write (it's an MVP!)
Don't need anything more fancy than this.
* Tried Redux / Redux Toolkit enough to realize for a MVP it's sufficient to just hack stat with hooks and contexts, reducers are too much b
Re: Ask HN: What would be your stack if you are building an MVP today?
#565Rails if I want a database, Sinatra if I don't. Ruby just... wants you to be happy while you're using it. And in the long run of life, that matters. Python wants to be correct, Java wants you to not make mistakes, JS is still figuring itself out, Scala wants to do hard things... Ruby wants you to be happy. IMO - There's a lot of very worthwhile follow-on effects of that - everything from libraries (generally) being j…
I was a Rails, Sinatra, Ruby dev for years and I’ve been work with Go for years too. I’m struggling to understand your perspective because I’m no less happy coding in Go.
I've only done a bit of Go. I liked some of the ideas that were present, but ultimately (and I believe explicitly) Go has computer-sciencey-correctness goals (hence all the kerfluffle over generics) that, now and again, trip things up.
Sometimes that's really nice - we had a handful of tiny utilities written in Go, like a format converter for use in a datastream - other times it gets in the way. I don't think I'd want to code up something large in Go, although it's not something I've had the opportunity to try.
AFAICT, Go believes in preventing you from making certain mistakes. And usually, within it's context and paradigm, it's correct to do so. The problems arise when your problem domain doesn't line up well with that context and/or paradigm, which sometimes just comes down to the time you can spend on the issue.
Another example: IMHO, all the weird issues Go was having working out how to do package management stems from some (admittedly very cool) ideas about Correct And Proper Package Management. I can't remember the last time I had an issue with gem management / bundler (except for the perennially awkward PG gem issue).
It's a 85% vs 95% thing, and IMO that straight-up comes from having other priorities. There's a lot of overlap between "developer happiness" and "computational correctness", but it's not exact, and that comes up in few, but enough, places.
Maybe another good example is Ruby array arithmetic. It makes no bloody sense from a math/CS perspective, but goddamn it is handy in applications. So if your language is aiming for computational correctness, you're not going to get that tiny bit of joy.
Re: Ask HN: What would be your stack if you are building an MVP today?
#566I 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/ ).
Next time check out Avo. It integrates perfectly with Jumpstart (or any Rails app) and helps you create a back-office app in no-time. https://avohq.io
I've checked out Avo several times before. I don't need it quite yet.
It looks beautiful Adrian.
Re: Ask HN: What would be your stack if you are building an MVP today?
#567Definitely 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…
The one thing that Django is missing is the ability to attach a User object to a session without a full-fledged RDBMS. I wish it was structured like the Session object which you can in your own backends for.
This is unlikely to ever happen though since so much is tied to it like the permissions system and the admin. The ORM itself is central. I wouldn’t use Django unless your project depends on an RDBMS.
Re: Ask HN: What would be your stack if you are building an MVP today?
#568Google Cloud Run (with Dockerfiles) + CloudSQL (Postgres) + Cloud Tasks.
On the back-end, NestJS with Typescript plus some query builder such as Knex (TypeORM is pretty buggy). Or maybe even try Prisma.
For front-end it depends. I would try using just Vanilla JS with Tailwind if possible or fallback to React + Tailwind if there are too many screens, or they need a lot of updates based on state.
Those are mostly technologies I'm comfortable with because I use them every day. However, if I have the option to waste time researching and/or learning, I would research the state of server-side Kotlin and learn Elixir/Phoenix before making a decision. NestJS can ge too verbose sometimes.
Re: Ask HN: What would be your stack if you are building an MVP today?
#569- NextJS
- Tailwind
- Hasura / postgres
- DigitalOcean - docker droplet
- Caddy
- Cloudflare
Re: Ask HN: What would be your stack if you are building an MVP today?
#570After working with the PETAL (Phoenix, Elixir, TailwindCSS, Alpine.Js, Liveview) stack at $JOB for a while now, I have to say I've never been more productive. Early on I would still have to lean on Alpine heavily for various JS interactions but with all the features Liveview has been adding and improving on (Hello JS module!) I find myself needing it less and less. Liveview really has been a game changer for me. Tail…
I'll second this. Alpine.js is so nice.