zeemonkee2

5 ms·

1.
by zeemonkee2 14y ago
All other things being equal, a "homegrown" project by coders who know what they're doing is going to be better than a framework project by coders who don't. Yes, I understand your reason, and given coders of equal ability it may be true; b
2.
by zeemonkee2 14y ago
I said it makes no difference.
3.
by zeemonkee2 14y ago
What if you want to get rid of the username field altogether? For example, my typical use case: unique email address for logins, no usernames: I suppose you could subclass User with a longer username, and sync the username with the email ad
4.
by zeemonkee2 14y ago
I'm not arguing against using a framework, if it fits your project requirements, and we can argue the day long about micro-vs-full-stack. There are good arguments for both, they suit different people and projects. My own observation is that
5.
by zeemonkee2 14y ago
Sure, if you did it completely on your own. More likely you use Flask or Pyramid which provide the plugins/entry points/templates to make wiring these components together quite easy.
6.
by zeemonkee2 14y ago
It's a long-standing tradition for DjangoCon to have a "Why Django Sucks" presentation. And a healthy one IMHO.
7.
by zeemonkee2 14y ago
Really, it's more of a management problem than a coding problem. Short-term thinking, bad hiring/outsourcing practices, and poor client expectations management, among others. A framework or language isn't magic pixie dust that will make the
8.
by zeemonkee2 14y ago
Most codebases I've seen that are badly maintained or managed over the years are horrible messes - whether Django, Rails or anything else. The last codebase I worked on - written in Django - was appallingly bad. That's no fault in any way o
9.
by zeemonkee2 14y ago
> I think people who criticize Django have yet to make up their minds about what a framework is all about, and what, if anything, it's for. They just hold on to their utopian idea of what their framework should be. No, they have a diff
10.
by zeemonkee2 14y ago
> Django templates are sloooooow. Jinja 2 is an order of magnitude faster Template execution speed is unlikely to be the bottleneck for the vast majority of sites. I prefer Jinja2 for the flexibility (macros etc) rather than the perform
11.
by zeemonkee2 14y ago
In Python, you wouldn't reroll your own ORM, routing and templating - you'd use SQLAlchemy, Werkzeug, Jinja2/Mako/whatever.
12.
by zeemonkee2 14y ago
Agree on Django auth; it's horribly designed - need an extra field - use a separate UserProfile - really? Need to login with unique email address - which EVERY SINGLE client asks for - you're going to go down a rabbit hole. A group/permissi
13.
by zeemonkee2 14y ago
Sounds like a good idea, however to sell at BigCo: - you really need contacts. As the OP points out, this involves working with them some time (in the inside, as contractor, selling to them, whatever). If you haven't, find a salesman who ha