News for hackers. Stuff that matters.

A comment on Rails, still?. Parent comment

Re:Rails, still? by toyg on Saturday September 01, 2018 @12:01PM (#17892421)
There are situations where Flask is good enough and very fast to deploy, while Django is overkill and more complicated to set up.

I agree that, should a system get significantly complex, eventually you will want Django; but a lot of projects simply never get there. That's why it's good to have a choice anyway.

[ Parent | on HN ]
Re:Rails, still? by sametmax on Saturday September 01, 2018 @12:33PM (#17892605)
Anything that requires auth or database access requires setup that a lot of dev will get wrong.

E.g : sqlalchemy sessions are very often badly handled. Of course you could write sql by hand, but then you loose the entire ecosystem of blueprints.

[ Parent | on HN ]
Re:Rails, still? by mixmastamyk on Saturday September 01, 2018 @02:27PM (#17893248)
> you loose the entire ecosystem of blueprints.

Blueprints for models?

[ Parent | on HN ]
Re:Rails, still? by sametmax on Saturday September 01, 2018 @05:57PM (#17894096)
Yes. E.g : sqlalchemy admin.
[ Parent | on HN ]