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

371–380 of 736 posts

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

#371

Post by sph »

ElfinTrousers wrote: post #112
sph wrote: post #63

Earlier quoted context omitted.

At the core there is a custom crawler written in Rust, with the goal of eventually releasing it as an open source standalone application. But everything else, including scheduling the execution of this crawler, and parsing its output, is done on the Elixir monolith.

Would that be in Rust for performance reasons? Elixir IME isn't as slow as some other popular languages but it's no speed demon either.

Performance has nothing to do with it. You can imagine the application being a very specialised version of `wget`, and I like CLI system applications to be easy to distribute, with no dependencies and not requiring an entire VM to run.

Erlang/Elixir is good for networked servers. For CLI apps I either choose Go or Rust, and I much prefer the latter. Since I want to make this component open source, I wanted to keep it separate from the rest of the closed source, proprietary Elixir backend.

There is no wrong choice to be honest, this is mine for my startup, and I don't think I need more justification than "I am productive with it for the task at hand."

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

#373

Post by kcartlidge »

moxplod wrote: post #86
mindcrime wrote: post #68

Earlier quoted context omitted.

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…

First I heard of HOTWIRE. I have been using PJAX for a decade now, which is a similar concept. I use .net mvc with a razor templating engine. But this can be used with any backend. It makes it super easy for me to maintain all my UX in server-rendered HTML templates. I get a clean SPA with super high development efficiency with MINIMAL javascript. The best part was I could hire any developer and they know how to work…

Worth looking into Hotwire. It works well with .NET MVC.

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

#374

Post by didgetmaster »

RussianCow wrote: post #287
shireboy wrote: post #261

Earlier quoted context omitted.

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.

For an MVP, none of those things matter. Just rewrite it in a different stack later if you realize that the one you picked doesn't fit your requirements long-term. Worrying about that stuff before you have users/customers is just a waste of time and energy.

But does that really happen? It seems that we have a lot of bloated, buggy, inefficient code out there because it was initially built using something that was 'quick and dirty' for the MVP and was never rewritten properly once it caught on.

I have clients that still use Excel spreadsheets for their database instead of using a real one just because their data was initially stored there and they never changed. New features were added incrementally over time and it became costly to break everything for a complete rewrite. So they limp along forever because management won't let them do it right until it absolutely breaks.

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

#375

Post by gmassman »

nicbou wrote: post #206
ultrasounder wrote: post #172

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…

Agreed, although I'd really like to throw in type safety, because the lack of it made my life needlessly complicated. Is this feasible with Python?

Type hints in Python are nice, by pale in comparison to truly typed languages. If you want to feel like your language’s type system significantly improves your development experience and the safety of your code, don’t pick Python.

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

#376

Post by m0llusk »

Basic REST inspired service made with node and expressjs implementing business logic based interfaces and all data stored in Postgres. Most objects get UUIDv4 identifiers. Logging is with pino. Everything gets kept simple as possible so that junior developers can easily handle operations, basic extensions, or debugging.

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

#377

Post by agumonkey »

ultrasounder wrote: post #172

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…

do you still use builtin views/templates ?

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

#378

Post by squidsoup »

clint wrote: post #309
ultrasounder wrote: post #172

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…

For context I'm someone who spent nearly 20 years doing almost exclusively python dev, attended the first DjangoCon in 2008, ran the Django community blog during its formation heyday back in the mid 2000's and built tons of Django modules, apps, sites etc, have commits on the Project from way-back, tech edited Django books, etc... Did rails for a short while in 2010-2012 and absolutely hated it then spent 2012-2020 d…

As a long time python dev, I’m now not certain why I would use python for a web app, over typescript on Next, other than familiarity. Sharing types between the server and client, and only having to manage _one_ software ecosystem is great.

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

#380

Post by marcus_holmes »

jamal-kumar wrote: post #269
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…

yeah, I get the same - I'm probably not going to get something up as fast as I would if I used Rails (though it's probably close - I've built so many sites on this stack that I know all the pitfalls and have a lot of the boilerplate down to copypasta now).

But this backbone can take a lot of experimenting with features easily, and is fast enough to forgive a lot of sins - I generally just don't have to worry/think about performance at all.

Post reply on HN