HN Explorer

Djangy Is Not Good

3 points by alnayyir ↗ HN
Got invited to Djangy beta, sign-up link raised 500.

Worse:

They're running debug=True on a production deployment, and the error was a painfully simple import error (basically, urls file wasn't found).

How am I supposed to trust these people with managing my apps?

I keep feeling like my industry (web dev) is some kind of 24/7 Amateur Hour when things like this happen.

8 comments

[ 3.4 ms ] story [ 30.8 ms ] thread
mikelbring
Tell Heroku?
jgoewert
I don't think the people at Heroku would much care... except that their name is being sullied by this clone.

Anyone reading this will equate Heroku to a steaming pile because Djangy is being alluded to being one.

Could this topic be renamed to Djangy is horrible instead of "Heroku for Django"?

alnayyir
Djangy, I was referring to it being a heroku for Django
jnoller
This is not the place to file bugs; or vent when things are broken. It's brand new, bleeding edge - your feedback is better sent to the developers. Flagged.
alnayyir
Flag yourself, I emailed them and they sorted it out.

I think people would like to know if they're going to show this much lack of care.

debug=True should never ever ever happen in a production environment. Very sloppy.

wccrawford
It's a BETA. You aren't supposed to trust them. You're supposed to play with it and try to break it. Congrats, you broke it twice. File bug reports.
alnayyir
Beta usually mean it works, and debug=True should never ever go anywhere production.

I don't think you're a Django dev, because that's a srsface problem.