Interview with Python founder 1: about Django and Ruby

HOST: Chris DiBona (head of Google open-source website) and Leo Laporte (founder of twit website)

Interview: Guido van rosum (founder of Python)

LEO: Python lacks some local GUI Libraries, only TK or something. Do you think this is a problem?
Guido: Now this is no longer a problem because more and more people are using the Web to do anything.
LEO: Web is the interface.
Guido: but it does not solve any problems. As I said, "Python web frameworks have more keywords than other languages." I personally like one of them, this is also my long-term choice. The framework is Django.
Leo: I'm going to ask you about Django. Someone recently wrote an article. I think it was first introduced on the rails website. It tested Django, for rails and Perl web frameworks, Django is the fastest, far surpassing others.
Guido: This is very interesting. I have never heard of it.
C: How do you test a Web framework?
LEO: they set up some web test applications and set up a series of transaction test cases to test transaction operations. Django is fast and fast. Let's talk about Django.
Guido: I am a very satisfied user with Django and used some Django in the project. I call Django the "second generation" Python web framework. The first generation refers to Zope and twisted. Django was developed by two young people working at the Kansas news agency, it is not a very famous place.
CHRIS: It's strange that Zope and plone are also from newspaper websites.
LEO: They want to streamline their workflows, which is very important to them.
Guido: Maybe this is the reason. The newspaper in Kansas wants to build a local website that provides information to local people. The website must respond very promptly to readers and publish content quickly, rather than simply posting an article to a website, anyone can do this. It must easily change the appearance of the entire website and add new ideas and new features, add new applications. For example, releasing local sports events and providing a variety of interesting information about the team's links and photos, they hope this will work very quickly. I think they have been doing this for two years. These two boys work with a group of editors to provide them with content. At the same time, they felt it was necessary to build a framework. They extracted the framework from their first website application. By editing their constant demands for website modification, they added better flexibility to the Framework. Later they decided to say "let's open source" and their ideas were supported by the newspaper. Then interesting things happen. I think the newspaper is still using Django in part. These two guys may no longer work in the newspaper. They started the Django open-source project. I think the best thing is that I have talked to these two people several times and read their demos to learn how they work. They have indeed achieved open source. They have good license agreements. For me, the most important thing is that throughout the process, the way they operate the user community, their practices, they seek a balance between chaos and democracy, it allows many users to add functions and provide ideas, but does not lose the flexibility of the original ideas and frameworks. I think it is great to make Django a better product, this is far beyond what Kansas needed at the time.
LEO: The test was conducted on the Ruby on Rails wiki website.
Guido: Can I access it now?
CHRIS: the Wiki of Ruby on Rails cannot be accessed.
LEO: No, it's there. The article is about framework performance. The Django website's link to this article is bad. They tested symfony, not the Perl framework, it is a PHP Web framework, and rails, Django, and Django are dozens of times faster.
Guido: Wow, I know that the Django development team has spent quite some time making their template mechanism run quite smoothly.
LEO: Of course they use modpython for better performance.
CHRIS: modpython is an Apache Python module that makes Python running faster.
Leo: I want to see Django. It's really impressive.
Guido: Of course, I strongly recommend it.
Leo: I have also seen turbogear, and I often go to a website called doggdot (http://doggdot.us/) which is made with turbogear.
Guido: What is the name? This name is too ugly.
LEO: doggdot. US combines Digg, Slashdot, Del. icio. us into, which is written in turbogear, is another Python web framework. It seems that there are many other Python web frameworks.
Guido: Oh, it seems that turbogear and Django are currently competing for the market share of Web Development
Leo: I like Ruby on Rails. One reason I like Ruby is that it looks like python in many ways.
Guido: indeed, it looks like python
LEO: of course, but its object orientation starts from scratch. Everything is an object (everyting iS object)
Guido: In pyton, everything is also an object (everyting iS object), but not everything is a class (everyting iS class), because this is my favorite method.
LEO: Let's talk about this. Why do you like this?
Guido: Because not any programming will naturally adopt an object-oriented method, for example, a very extreme example. Unfortunately, writing a helloworld program in Java requires six or seven lines of code, you cannot avoid declaring a class because the method must be defined in the class, which requires a lot of input.
LEO: In Ruby, numbers are also objects.
Guido: in Python, the same is true.
Leo: Yes? It is easy to overload some functions in ruby, so that the object-oriented approach is clean and concise.
Guido: The difference between Ruby and python is that in Ruby, you always define functions in the class. If you do not specify the class to which the function belongs, then you may define functions in a default class. In python, all data objects are classes, but you can define functions outside the class, such as module ), as the namespace of a function, a function is an object and a module is an object, but they do not work as a class. This implementation is just a different choice than Ruby.
LEO: you must have your reasons for doing this.
Guido: Recently I have heard some complaints about Ruby, which surprised me a little. Ruby execution speed is much slower than that of Python. I think this affects some of the performance test results you just mentioned.
LEO: And Ruby threads are not localized, which is indeed a big problem.
Guido: Oh, my God.