Hacker News Reader

> "JUST USE RAILS FOR NOW."

That could also be reduced down to "JUST USE RAILS".

Why not get the best of both worlds where you finish projects AND be happy about it? The "for now" makes you think it's a bad decision and you hacked something together to get it done.

But you can finish, stick with Rails and be insanely successful based on what's important to you (start, finish, maintain, profit, IPO, etc.).

You convinced me: JUST USE RAILS. It's printed out.

Some of the "right" tools are right only in context of a professional team anyway. Especially true when deciding how to organise a project.

If it is just me, for me, I will write it simply and from scratch or use a familiar general purpose framework like rails or laravel. One I have lots of experience with so the project actually gets done, instead of spending all my energy learning another new tool.

Or for us Pythonistas, just use Django. Heck, even if it's just a simple REST API (using DRF), I often do it as the project tends to grow.

If only there were something similar for Node, or Rust.