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

101–110 of 736 posts

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

#101

Post by mlboss »

iamsanteri wrote: post #64
physicsguy wrote: post #15

Django, in my previous role we did MVP websites for academics and the speed of getting a site up and running and deployed was just so fast. I’ve never worked with anything else that is as fast, anything like FastAPI or Flask or Express or similar either requires additional libraries to add really basic and common functionality or you have to roll it yourself. I personally don’t think that if you’re building an MVP yo…

I‘m trying to learn Django just for this kind of MVP purposes. I also did a small mini project in RoR by following their documentation. Is there anything that is significantly easier to do in RoR vs. Django? Alternatively, is there anything, say, on a larger scale that I can do with RoR that I cannot do in Django if the project grows? These are the questions I‘ve been wrestling with quite a bit now. After learning Vu…

If you thinking of anything closely related to ML then python/django is the way to go.

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

#104

Post by jmuguy »

mindcrime wrote: post #68
lta wrote: post #32

Earlier quoted context omitted.

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 vaguely aware of htmx, but have never used it. Had not heard of hotwire until just now, but that looks really interesting. Thanks for the pointer! Would you care to say any more about your experience with Vue? I've heard a lot of good things about Vue and had it on my mental "things to learn one day" list for a while. Would be really interested in hearing any counter-points from somebody who hasn't enjoyed workin…

I'm not sure what their particular beef with Vue is but I've been using it for several years now with Rails and its mostly been great.

They had a similar issue as Python, albeit not nearly as bad, with their upgrade from version 2 to 3. It required some rewriting. They also introduced a new core concept with the "composition" API, which completely changes the way Vue apps are written. Luckily once you made a few required changes you could continue writing apps like you used to, ignoring the new composition API. I'm assuming at some point we'll be forced to change, which will suck.

One thing we do, which I don't think is as common when using Rails with a heavy frontend like Vue or React, is that Rails is not in API mode. That is Rails still handles routing, pages are still rendered in ERB, and then each page is its own little Vue app. So we can use Rails, Ruby, etc to initially hydrate the pages and inject stuff by calling to_json on it. This also means we can let Rails and Devise handle login and session, which I absolutely hate doing with a pure JS frontend.

Routing and session management are something I think Rails is extremely good with. This also means that if a section or sections of the site are pretty simple (password reset for instance) we can just render the page in ERB, no JS required.

Regardless, I still like Vue and it has a pretty decent ecosystem. If I had to go back and start again I'd probably just go with React. It clearly has the most support (and most jobs) on the front end.

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

#105

Post by fatnoah »

MobileVet wrote: post #42
nvln wrote: post #9

Earlier quoted context omitted.

I'm building the MVP to make a product and get some market feedback / validation.

Then build what you know… always the fastest choice.

I agree with this. .NET isn't sexy, but I can do it in my sleep. Throw in a reasonable front end framework, and I can spend my time getting feedback and iterating. Once I need to grow and scale, I'll put more thought into the right tech for that job.

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

#106

Post by jrvarela56 »

bottlepalm wrote: post #100
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,…

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…

Ah you comment about MUI reminded me to include Mantine, also big productivity driver.

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

#108

Post by logifail »

> What would be your stack if you are building an MVP today?

Many years ago a CIO told me he didn't really care what technologies I picked for an upcoming MVP backend, as long as I was already comfortable with them and would therefore be productive quickly.

He also told me we would almost certainly need to rewrite everything at least once, so not to dwell too long on the initial stuff.

Build the MVP, build it quickly, get it in front of users. It just needs to work, you're not going to get marks, or customers, for backend coding style.

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

#109

Post by treis »

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…

IMHO, part of this is that people have accepted the poor experience of non-realtime applications. But there's a huge UX improvement if the application responds faster than users can input actions. Doesn't matter for all applications but if your users are going to spend significant time inputting data it makes a huge difference.

Also IMHO, a flexible type system like Typescript makes development faster than without it. You can refactor faster, it catches silly mistakes, and you don't have to write as many tests.

Rails does a lot of great things for you, but IMHO ultimately it's stuff you don't really need. If there's any chance that the application will grow beyond a few developers I think it hurts more than it helps.

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

#110

Post by mlboss »

Django/Postgres/htmx(for interactivity) . I was able to release aipaintr.com in 3 weeks working 2-3 hours daily.

All the new fangled frontend technologies make me dizzy :). On top of that this is my fist project in django.

There is a nice django starter oss project called djangox which takes care most of the integration out of the box.

For a new project the complexity should be on the marketing stack. Choosing a good tech stack is a distraction. Choose something that will allow you to create MVP fast and then start marketing.

Post reply on HN