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

261–270 of 736 posts

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

#261

Post by shireboy »

thecodemonkey wrote: post #22

I would pick whichever stack that I would be most productive in. A Laravel app hosted with Laravel Vapor (AWS Lambda) with a MariaDB database. Would allow me to get up and running quickly, at low cost and without having to worry about scaling for a long time. Using Tailwind and VueJS or AlpineJS for the frontend.

That’s usually my take, but I still worry about a few things:

* which stack will still be around in 1/2/5years?

* which stack Will other teammates or future devs be productive in.

I’m still searching for a very light, productive open source stack that is well accepted and if not future proof at least we’ll backed.

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

#262

Post by 0xblinq »

blascsi wrote: post #182

I've been trying to put together a solo project, that might be worth launching a bit later. My stack in general is: Elixir for the backend. Reasons for it: - Elixir is designed for reliability, so since I want to keep the app alive as much as I can by myself, it seems like a great fit. - It also has excellent integrations with Postgres (my choice of DB) with Ecto. - I generally skipped Phoenix, as I'm just using Elix…

My issue with Phoenix (or Elixir..) is that there are like 3 people in the world using it. The community and the third party packages available is minimal compared to other ecosystems.

And in my opinion, it is already past its best days. I know of several companies in my area that a few years ago chose it for building their services and ended up, or are migrating to other stacks because of their problems hiring.

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

#263

Post by wonderwonder »

My last SAAS was just raw php on the backend with postgres. Raw JS on the front end with a little JQuery. Ran for 9+ years, zero down time, zero issues. Supported the Marketing and legal department of a Fortune 500 company. Old school is they way. It does depend on what you are building though.

Recently really started to like Python so would probably try DJango.

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

#264

Post by thomasqbrady »

jrvarela56 wrote: post #85

Personally big on Rails (use it at work every day). But, my last MVP I did with TS/Next/Mantine/Supabase/Vercel. Reasons: - I've been using Rails as an API only, so having to grok views felt like a waste. My React skills made me feel that learning how to make complex views in my backend was a waste of time. - One type of bug I hate is ensuring my API calls have the right schema. With Supabase and TS in the frontend,…

What's RLS? Row Level Security?

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

#265

Post by adrianthedev »

aantix wrote: post #140

I 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

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

#266

Post by brookst »

randomh3r0 wrote: post #253
brookst wrote: post #202

Earlier quoted context omitted.

Eh, I think experimental physicists and medical imaging also lean towards newer tech.

Eh.. you'd be surprised. Medical Imaging isn't as radical as you may think it is (I spent 7 years doing projects for the exploitation of medical images).

I’ve had the pleasure of annual echo cardiograms my whole life, and moved around a lot, and at least my experience has been visible hardware/software/imagine improvements almost annually.

In any event I wasn’t saying all medical imaging is state of the art, I was saying it is another field where people prefer newer tech.

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

#267

Post by vishnugupta »

I'd say hybrid-ish.

1. Hosting, full on AWS. Because I'm super comfortable with it and I get end to end; from domain registry to data store and everything in between.

2. (mostly old school) Web app stack: React, Java/NodeJS, Postgres. S3 for doc store fronted with Cloudfront. Reason: Battle tested, huge and thriving ecosystem, most of the problems are solved.

3. Lambda for async tasks.

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

#269

Post by jamal-kumar »

marcus_holmes wrote: post #254

Go & Postgres on the backend, running on a baremetal server. Because this is actually capable of handling a decent workload for really cheap compared to cloud. There's a few tricky bits to do with logs and reporting, but the benefits outweigh the pain. Vue on the frontend. Last time I used BootstrapVue and it worked well. I'd want to re-evaluate that decision next time, have a look at some of the newcomers. I'm aware…

I'm of a similar philosophy, but also because I'm not beholden to rushing a minimally viable product to the feet of some angel investors (Super allergic to that after a few experiences). I mean it's kind a a premature optimization if you just need to get a working example out there for people who like to see fast results, but if you've got the funding to start your own company just writing it properly for performance from the get go is the obvious thing to do.

I also choose a stack like that because it's what I've been mostly working in for a long while now and it's really productive (For me).

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

#270

Post by 0xblinq »

lta wrote: post #32
gls2ro wrote: post #20

If it is a SaaS 100% Ruby on Rails Why: - has almost everything that I need usually in mature gems - battle tested in production - speed of development

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…

I'm using Laravel with Hotwire and it's fantastic. Now I want to cry every time I see the mess of overengineering I have to deal with in other projects when they're built with Redux, React, etc, etc.
Post reply on HN