On Oct 19, 3:59 pm, "Kevin Cole" <[EMAIL PROTECTED]> wrote: > On 10/19/07, Ben Sizer <[EMAIL PROTECTED]> wrote: > > > Just a suggestion though: I think there's a slight overreliance on > > referring to other technology, like "model objects following the > > Active Record design pattern, and using a DSL syntax". It's speaking > > to experts rather than beginners. I think that these terms will mean > > nothing to many people who are just getting started and may make them > > think that using Elixir is a complicated and jargon-filled task, when > > in fact it's very simple. And it tells you what it is, as opposed to > > what it does. > > > A first draft at something I would consider better would be "Elixir > > provides the ability to create simple Python classes that map directly > > to relational database tables, providing many of the benefits of > > traditional databases without losing the convenience of Python > > objects. It is a declarative layer on top of the SQLAlchemy library, > > and is modelled on the Active Record design pattern with a simple > > syntax similar to that used by Ruby On Rails." > > Well, in my case " It is a declarative layer on top of the SQLAlchemy > library, and is modeled on the Active Record design pattern with a > simple syntax similar to that used by Ruby On Rails," doesn't mean > much either. ;-) Sad but true. I always feel like these "better" > technologies tell me how much better they are than X but then want me > to go learn X anyway so that I can understand why I should unlearn X.
Yes, I totally agree. I left that second sentence in so that the people who know about Ruby on Rails and Object-Relational Mapping patterns and all that stuff could see something they identify with. Most mere mortals won't know anything about that stuff though, which I think is often lost on those who write wrapper libraries for interface libraries for back-end databases based on another language's standards! (No offence intended to Gaetan et al.) Hence me trying to suggest a way in which they could word it to make sense to the inquisitive visitor, rather than just the experienced developer who's already familiar with the alternatives. The first sentence I suggested emphasises that essentially Elixir is a library that backs Python classes up with a relational database back-end. Hopefully that is something that strikes more of a chord with the typical developer. -- Ben Sizer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
