> Not to go off topic, but it's become pretty clear that there are > important advantages to cooperation (in terms of traditional natural > selection, and in economics, etc). Furthermore it is pretty widely > accepted that the advent of language -- and the massively improved > cooperation it allows -- is at the heart of the explosion of human > populations in recent pre-history. > > So, if evolution rewards those who learn to cooperate better, it's > probably not comunist to say so. :)
I completely agree with you. The ideal scenario would be as much cooperation as possible. If an API is written in a flexible way than pieces can swap in and out. Healthy innovative competition is much different than destructive competition like wars etc. Just like at Python for a model of innovation..how many ideas in python came as a direct result of borrowing for other languages...perl for regex, java for unittest etc. This is good and healthy and not matter what anyone says, there is going to be constant innovation..and "disruptive innovation". I think the way to cope with this model is to expect constant change and healthy competition and plan around it. There are already several people working on a Storm based web application framework in Twisted. What to do...? Just accept it and see if they come up with some good ideas that can be used further down the road. Time will ultimately shake all of this out, and the "market" will decide the winners. Look at Turbogears and Pylons, there is a "merge" of many of the same technologies and both sides win. I am sure something like this will happen in the next 2 years. The best ideas from all the ORM's will surface and eventually make a couple of strong ones. It is a process no one can control, but the "market". > > And, isn't this what happened with Ubuntu and Linux generally? We > learned that communities composed of individuals cooperating can out > perform highly directed, highly competitive organizations like > Microsoft by creating compelling software releases on a 6 month > schedule. > > The TurboGears folks are cooperating with the Pylons folks, there's at > least been some talk of the DejaVu and SQLObject folks cooperating > with the SQLAlchemy people in the future. So, hopefully there will > also be an opportunity for the Storm and SQLAlchemy communities to > work together and learn from one another, and this will be an > opportunity for productive discussion of the technical issues, and not > devolve (as I'm a bit afraid it will) into a flame war between > zealots. > > So, in that spirit, I haven't had time to investigate Storm in the way > that I would like. Can anybody provide a list of actual technical > advantages that it has over it's competitors like SQLAlchemy and > DejaVu? I personally think it would be cool if the Turbogears API was high enough that it "expected" drastic innovation at say a 6 month cycle like Linux. When a distruptive technology appears, then it just accepts it. That seems like the best approach for Turbogears. As soon as anyone thinks "this is the best and only way", then innovation stops. There is no best way, there is not one way. The way forward is to accept change and disruption....otherwise we prove we are getting too old :) > > > > -- http://www.blog.noahgift.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
