You can build basically any MVP in almost any programming language and platform. That said, anybody who gives an answer without knowing what they're building first and knowing the tradeoffs involved IMO isn't doing things right.
Ask HN: What would be your stack if you are building an MVP today?
621–630 of 736 posts
Re: Ask HN: What would be your stack if you are building an MVP today?
#622Earlier quoted context omitted.
I’m keen on this approach for my next project. Can you share any Dockerfiles / scripts you use to get going with this?
Sorry I do not, although I have been meaning to publish the "skeleton" template repo's I have locally. There are two template repos I use: `web-ui` and `server` The both have a `sh` dir with common commands in .sh files (watch tailwind, watch esbuild, browsersync to serve and live reload during dev). You config Google Container Linux with a `cloud-config.yaml`, which can take a bit of time to tailor at first, but aft…
Re: Ask HN: What would be your stack if you are building an MVP today?
#623HTML, css, js, (maybe jquery and font-awesome if I want to get fancy) and all static files dumped in an S3 bucket for as long as I can get away with it, then django if I need anything more. Not that I think python/django is the "best", but it is what I know and it's got all the batteries included out of the box. I've never made a sufficiently advanced UI that required react/vue/etc. So I still just stick with html/cs…
I wonder why people like s3 buckets. if your website becomes viral it might become expensive
Re: Ask HN: What would be your stack if you are building an MVP today?
#624Earlier quoted context omitted.
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?
#625Earlier quoted context omitted.
I'd argue the other way. Yes anyone with a can-do can learn Elixir. But there's a difference between learn and LEARN.. I work with a pile of rails devs writing code in elixir. In that I mean you can feel the rails in their code. It "tastes" like rails. A few python devs also write python with elixir syntax. Finding people who know the language is hard. Finding people who are willing to risk their time on the language…
Isn't Elixir a little bit like Ruby though? At least superficially. And it supports metaprogramming like Ruby. So I'd guess the code would end up looking similar on a lot of teams
You can know enough to get going quickly, but there's a healthy layer of power that will only come with time.
Re: Ask HN: What would be your stack if you are building an MVP today?
#626JAMstack for the frontend served via cdn
Terse STATELESS apis on the backend likely in Go on a managed k8s cluster
DB choice depends on requirements for the app IMO if its data that needs to consistently persist put it in a relational DB like maria or postgres. If the data is short lived let it hit mongo or otherwise.
To be completely honest though with current tooling you could do an e2ee local sqlite database and store it in an S3 bucket using a guid per user.
Re: Ask HN: What would be your stack if you are building an MVP today?
#627Earlier quoted context omitted.
Thanks for the kind words. It’s probably time for me to revise that a bit, or write another one. I’ve learned a lot more yet since I wrote that. I used to use Flask, but I changed over to Django at the end of 2022. Super happy I did. It wasn’t painless, but the benefits have been totally worth it.
What were the benefits switching over to Django from Flask?
Built in migrations. Can’t possibly overstate how much this has helped ease deployment. Most of the live debug and prod edits I had to do on the older app were due to db migrations not being shipped with the app.
A baked in ORM with lots of backend optimizations like pagination that keep your queries fast, plus convenience functions for model creation and retrieval (long live get_or_create)
There was a learning curve to all of this, and the complexity of all this in the tutorial scared me away at first, but having seen how the other half lives with Flask, where there are no guardrails for anything, I really appreciate having a framework that solves these kinds of challenges for me.
Re: Ask HN: What would be your stack if you are building an MVP today?
#628Earlier quoted context omitted.
(supabase ceo) We definitely like to receive feedback for improvement. let us know what you're frustrated by @leros. Sometimes there is context for the restrictions which we haven't shared in the docs, so it would be great to hear it so that we can either fix or clarify.
I'm not unhappy about anything in particular. Superbase is fantastic and many of the upcoming things are things that I'm excited about. It's just that something I plan to work on for a long time, with lots of people, and that will have lots of business and scaling complexity, I prefer to run my own simple stack so I have full control and don't find myself waiting on someone else's roadmap for a feature I desperately…
Re: Ask HN: What would be your stack if you are building an MVP today?
#629Earlier quoted context omitted.
I'd argue the other way. Yes anyone with a can-do can learn Elixir. But there's a difference between learn and LEARN.. I work with a pile of rails devs writing code in elixir. In that I mean you can feel the rails in their code. It "tastes" like rails. A few python devs also write python with elixir syntax. Finding people who know the language is hard. Finding people who are willing to risk their time on the language…
Isn't Elixir a little bit like Ruby though? At least superficially. And it supports metaprogramming like Ruby. So I'd guess the code would end up looking similar on a lot of teams
It's not object oriented, it's a functional language. It is polymorphic and all data is immutable. (Edit: actually realised its very much not like ruby, when I re-read this)
What I've seen in most projects is that the awesomeness that is threading (tasks and processes) is not really used. Supervisors aren't built as first class citizens.
I see teams eat the cost of NIH, but not get the benefits of crash fast, crash often.
So yes it does end up looking/smelling like ruby/rails but it really really shouldn't.
“A language that doesn't affect the way you think about programming, is not worth knowing.”
Re: Ask HN: What would be your stack if you are building an MVP today?
#630Earlier quoted context omitted.
Isn't Elixir a little bit like Ruby though? At least superficially. And it supports metaprogramming like Ruby. So I'd guess the code would end up looking similar on a lot of teams
There is development joy found in both, but Elixir and the underlying erlang definitely has it's own idioms. You can know enough to get going quickly, but there's a healthy layer of power that will only come with time.
I should mention there is no problem not going there. I respect my teammates. Ruby/Rails is a great way to get things done. I would 100% use it as my MVP lang.