> You're too diplomatic. The reason is that the Django guys -- who are > far better hackers than I -- NIH everything. I can understand their > reasoning, but that's why code isn't shared.
They want a silo they can control, so they can manage things and provide the tightest integration possible. I personally don't agree with that philosophy for a web framework, but I respect their choice, and I'm sure that it has a lot of benefits. My main objection is that innovation happens at the edges, beyond the boundaries of your project/company/group and if you don't recognize that and stay open to code from "outside" you won't be able to compete in the long term. That's the specific philosophical difference which keeps TG and Django from working together more. And that isn't a problem with the Pylons folks -- they're very pragmatic about code re-use in the same way that the TG project leaders have been. --Mark Ramm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
