Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm no big fan of Django, but it sounds to me like you started using a well-established framework and whenever something was painful you chose to roll your own. Maybe a better approach would have been to engage with the Django community and help make these things less painful. That way your experience would benefit the next users, and you'd benefit from the collective wisdom and shared resources of a big and serious community. All other things being equal, rolling your own is rarely the right solution.


I only rolled my own URL routing. The complete implementation is less than 70 lines of Python.

Why am I obliged to engage the community when things are painful? I took an easier route: I choose less painful components.


I wouldn't say that you're obliged, but I'm sure they'd appreciate the feedback about what was painful and what wasn't.

Edit: I guess the article could be considered feedback :)




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: