Python code defines
the database tables, and this is generated from the same place that defines the attributes on a model object.
In Rails you define migrations for your models in Ruby, and then the attributes in the database are available
to your model object without you having to specify them. These are two slightly different approaches, but in
the end which one you choose doesn??™t matter much.
In summary, the big difference between the frameworks is in style and feeling, rather than functionality.
They are both perfectly satisfactory for most web tasks. However, if you want Ajax, Rails will probably give
you a big head start. Also, Rails runs on the JVM, but Django does not.
Seaside (Smalltalk)
It??™s hard to compare Seaside with Rails, because they embody completely different design and architectural
decisions. Seaside is a web framework based on continuations. Now, the thing that makes Seaside such an
interesting framework is that it inverts the usual way of writing a web application. Instead of having small
separate parts of functionality that trigger at different points in the life cycle of a web interaction, and maintaining
state by saving away small nuggets of information indexed by data in client cookies, Seaside lets you
write your web application more or less in the same style as you would write a regular command-line application.
You start up, initiating everything, then loop and let the customers specify products they want to order.
Pages:
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98