The right startup stack starts with your team
Rails, Django, Node, and Go users offered different answers. The useful part is the constraints behind each choice.
The takeaway
Customers buy solutions, not the popularity of your stack.
The context
The asker knew Go but was interested in Rails’ ready-made capabilities. Replies praised maturity and raised maintenance concerns. cardanome argued there is no universal choice; hiring, deployment, and product requirements change the answer.
Steps worth trying
Editorial suggestions, not promises made by the original author.
- 01
List familiar tools and the next three months of delivery requirements.
- 02
Prototype one real feature and compare delivery and maintenance costs.
- 03
Add complexity for concrete requirements, not hypothetical future scale.
Where this applies — and where it may not
This is a set of perspectives, not a framework benchmark. Versions, security requirements, and team experience need separate evaluation.
From the discussion
“There is no silver bullet that would fit every startup situation.”
@cardanome · View source
Ask HN: Would you still choose Ruby on Rails for a startup in 2025?
@dondraper36 · 193 points · 175 comments
Read the Hacker News threadSource: OpenIndex Hacker News dataset (ODC-By). Original content belongs to its authors. Summaries, translations, and suggested steps are AI-assisted editorial work. Read the sources; individual outcomes are not guarantees.