Live data from Hacker News

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

news.ycombinator.com

351–360 of 736 posts

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

#351

Well that depends a bit on what the MVP needs to be. Anything web related I'm probably going the Elixir/Phoenix route. I'm no web dev, but this combination makes me actually kind of like doing web-things with how batteries included it is, and the tools it provides to really jump start a project. Then I'd host it "old schoolish" in a VPS or similar since that's what I know best. Might consider being fancy and investig…

Agreed Elixir/Phoenix + Tailwind is at the sweet spot of scalability, performance, and bonkers productivity.

Real time? Need to go distributed? Maximize # of features / developer bandwidth? Cutting edge machine learning training & model serving?

Mobile? JSON APIs and GraphQL tooling is great, but https://github.com/liveviewnative is moving fast so this stack almost has the exodia of full stack, one language, and distributed actor model based scalability.

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

#352

Well that depends a bit on what the MVP needs to be. Anything web related I'm probably going the Elixir/Phoenix route. I'm no web dev, but this combination makes me actually kind of like doing web-things with how batteries included it is, and the tools it provides to really jump start a project. Then I'd host it "old schoolish" in a VPS or similar since that's what I know best. Might consider being fancy and investig…

LiveView is great but IMHO it's easily abused. "No JS, ever" is a mistake. IMHO it works best when there's very clear rules with where one should use LiveView vs JS.

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

#353
post #309

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…

Be aware that firebase or aws are only good until you have actual traffic. So in many cases you just loose time you spent understanding their managed infra. I would advice to go with Linode. As a bonus you get to lean new techs that are not tied to crazy managed pricing :)

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

#354
post #341

Currently building with Next/TRPC/Prisma/PG and would choose it again. I might be a little slower than starting with a full-featured MVC kit like Laravel or Rails, but having an e2e type system is so worth it to me. I do miss having a more mature ORM. I'm constantly tempted by Phoenix but desuaded by the lack of a type system. Does elixir somehow make up for the lack of types as a functional language? Also, I can reu…

There's a component called dialyzer that can help detect type issues, but i wouldn't say its nearly as useful as having real types in a language. That said, I've never found it to be much of an issue in Elixir, and the advantages you get with BEAM are worth it. There's a newer language called Gleam that does have a strong type system you may want to investigate, as it runs on BEAM (like Elixir and Erlang) and can use libraries and applications from both in its apps.

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

#355
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.

Rust also has the benefit of eliminating a ton of classes of bugs, which is great for the core of a product that connects to the network, fetches untrusted content, parses it, and (presumably) stores it somewhere.

Not that you can't still have bugs, but when you can get C-levels of speed with Python-levels of safety, why not?

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

#357

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.

> there are like 3 people in the world using it.

This is flat out untrue.

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

#359
Definitely still Rails for me, both for personal projects and for work. There are so many hidden requirements in SaaS products that have been baked into Rails and popular rubygems, getting to build on top of all that work is wonderful. It also makes coming back to a project to update it in a few months/years standard and simple.

If you haven't played around with Rails for a bit, things have gotten simpler in the past few years. Doing a quick demo/todo app on Rails 7 is delightful. With hotwire/stimulus, you get frontend performance that feels like React, but you're writing simple HTML/ERB templates and partials and some light JS controllers. It's quite nice.

Scaling those apps to lots of complexity is still an interesting challenge, and we're leaning towards React frontends on top of Rails APIs when the frontend is complex, but if you're building a standard CRUD app, Hotwire/Stimulus just lets you motor through the build and spend your time/money on user-facing value.

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

#360
Firebase (or maybe Supabase) - because I love a "backend-less" stack. It just take less effort (no need to write lambdas). Full solution out of the box (DB, auth, storage). If I ever reach the limit of this stack, I probably have insane PMF, so I'll deal with it then (YAGNI).
Post reply on HN