4 ms·
"Exactly right. This is not an argument to not use Django." No, but it might be an argument to consider frameworks that make it easier to replace parts as they
by jamesbritt 17y ago
"Exactly right. This is not an argument to not use Django."
No, but it might be an argument to consider frameworks that make it easier to replace parts as they become more trouble than they are worth.
- ubernostrum 17y agoFrom what I read, it didn't sound like he had much trouble. And, honestly, the various "swappable components" frameworks are basically in the same boat as far as I know: the ability to mix and match decreases dramatically once you've written application code, because their emphasis is on the up-front choices, not on swapping things later on.
- snprbob86 17y agoIt certainly wasn't easy. Although the vast majority of the difficulty can be attributed to porting application code, some difficulty can be attributed to Django. I would have preferred a framework which makes it easier to swap out components, but it is unclear how much it would have really mattered except for in terms of psychology.
- ubernostrum 17y agoWell, this is something I've been quietly agitating about for a while, because I have a feeling that your case is one where "swappability" doesn't help much -- once you've written your application code around a particular component, switching to another component is going to involve rewriting. How much rewriting may vary, but AFAIK there's nothing that can automagically port code, say, between popular Python ORMs.