Hacker News new | ask | show | jobs
by larryweya 4187 days ago
Already building one on Laravel 4.x and React for the front-end. Have a background with Django and my personal favorite Pyramid but Laravel really cuts down the boilerplate for me.
2 comments

Funny -- I'm going the opposite direction. I did a few MVPs last year on Laravel which have since moved to Django or Flask.

There is no admin generator I've found that compares to Django. And it is that time savings that is crucial in the beginning. It is shaping up to look like this:

Django and all the goodies on the backend (db migrations, admin generator, auth, rest-framwork)

Flask + SQLAlchemy OR Django-rest-framwork on the Frontend.

Sure, we might double-up on some models (Django models and SQLAlchemy models), but this works really really well.

I would argue that this is even better than using a BaaS for prototyping.

Could you elaborate on what kind of boilerplate Laravel helps you avoid compared to Django? My understanding is that Laravel is modeled after Rails.