On Sun, Oct 11, 2009 at 10:42 PM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: > > On Oct 11, 9:52 am, Russell Keith-Magee <freakboy3...@gmail.com> > wrote: >> On Sun, Oct 11, 2009 at 3:23 PM, Vinay Sajip <vinay_sa...@yahoo.co.uk> wrote: >> >> This is true, but again, the distinction between theoretical and >> practical problem emerges. The set of mainstream apps in the wild is >> much larger than the set of in house apps controlled by any >> company/group - so if the problem doesn't exist in practice for apps >> in the wild, the potential for the same problem to emerge in the >> smaller subset of in-house apps isn't that large. > > Fair enough, though I don't see how you could know the number of in- > house apps written by companies. I don't want to labour the point, > either.
If you can name a company that has produced more in-house Django applications than the number that is publicly available for download off the internet, I'll eat my hat. :-) >> I was referring to the fact that if your name is unique, it's easy for >> people to find it. Google isn't good at disambiguating, so it's in the >> interests of every project owner to choose a name that is unique. > > Yes, but I don't see the relevance to the disambiguation issue. You're proposing a solution to a name clash problem. If there is no ambiguity in names, then there _is_ no name clash problem. Obviously, it isn't as simple as that - there are _some_ ambiguous names out there in the wild. I'm just pointing out one of the reasons that name clashes aren't that big a problem is that basic Google-driven self interest acts as an incentive to keep the namespace relatively unambiguous. >> So we're talking about a hypothetical situation with two applications >> named tagging, which *both* need to be used in a single project, where >> *neither* application can have their name changed (either because they >> are both in the wild, and the self interest or because in-house >> policies won't allow a rename). >> >> Again - I don't deny that there is a problem in theory. I'm just not >> convinced that it is a problem in practice. > > I acknowledged at the outset that it was a hypothetical example, and > that I personally don't have that problem any more, though I did at > the time (way back when). I also didn't open that ticket originally, > so someone else at least would have come across the issue. But if > you're saying that since it's all open source and users can always > rename their modules (and references to them) to work around the > problem, then I suppose it's up to the community to say whether that's > a problem or not. And should this be posted on django-users, since > perhaps this might have bitten people who don't follow this list? I > presume the django-users readership is quite a bit larger than django- > developers. If this were a common problem, you wouldn't need to prod django-users - it would already be a recurring theme. To pick on a different ticket of similar vintage: the question of how to replace/modify/change the User model (#3011) comes up regularly. Some people want to allow email addresses as the username; some want to replace firstname/lastname with a single "name" field; there are many other requests on the same theme. The fact that the question is repeatedly asked indicates that a problem of some form exists. However, I can't recall the last time that someone asked the general question of how to avoid a name collision between their two tagging (or whatever) applications. I want to reinforce that I'm not morally opposed to this proposal or anything like that. If you want to pursue it, please do. I just want to give you fair warning that it's going to be hard to get any real movement on this issue unless you can get the involvement of someone from the core, and that is going to be hard to do unless you can prove that you have a real problem that needs to be solved. Personally, I think we have bigger fish to fry before we deal with hypothetical problems. Yours Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
