14
edits
(basically add a new proposal for a "mono" section) |
(added a new proposal for db section, add an item into frameworks section) |
||
| Line 1: | Line 1: | ||
== On Introduction == | == On Introduction == | ||
Typos: tookits -> toolkits, wory -> worry | Typos: tookits -> toolkits, wory -> worry. -knocte | ||
== On the majority of Cons sections == | |||
I propose to add the "dynamically typed" reason on all Cons sections of all dynamically typed languages (PHP, Perl, Ruby, Python). -knocte | |||
| Line 174: | Line 178: | ||
# '''Enforcement of Good Code''': The tools (Eclipse at least) do a good job. | # '''Enforcement of Good Code''': The tools (Eclipse at least) do a good job. | ||
== Proposed DB Section == | |||
We should discuss what to choose about persistence: | |||
* Relational database vs object-oriented database (for example [http://www.db4o.com/ DB4O], which can be used with Java or Mono). | |||
* If relational database is selected, support only one vendor (MySQL?), or n vendors, or use a higher level tool that supports n vendors? | |||
* If using a higher level tool to support n database engines, use object-relational mapping tool or code generators or stored procedures? | |||
== On Frameworks Under Investigation == | |||
It would be interesting to add [http://www.castleproject.org/monorail/ MonoRail]. It's a web development framework based on the MVC concept, following RubyOnRails best practices, but with the advantages of the .NET platform: being able to use the .NET API, the many .NET langauges, and the many .NET available libraries (like ActiveRecord or NHibernate). | |||
== Proposed Mono Section == | == Proposed Mono Section == | ||
edits