On Sat, 2006-18-11 at 16:17 -0800, JimmyDean wrote: > > Ulysses Almeida wrote: > > In example, since june I alredy saw TG switch the > > focus from SqlObject to SqlAlchemy and from Kid to Genshi. Ok, new > > technology are always cool, but if we change focus every time we see a > > new technology we will never have a "so waited" 1.0 version. We will > > be always throwing docs away and releasing inconsistent books (and I > > think the most of us prefer to write codes than docs, so trhow docs > > away really hurts). What I mean (and want to propose) is: Let's get a > > focus and finalize it. And to guarantee it, some one will need to do > > the BDFL hard work (Kevin?). > > It is true what you say, however, IMHO, if SA is really better than SO, > it would behoove us to adopt it sooner rather than later due to the > 'legacy' effect. The longer something is out there (higher version > number) the harder it is to be 'agile' and change tack. I am a recent > Java-to-Python convert and am looking very seriously at TG for some > major projects. But I have found SqlObject to have very poor > documentation. I would volunteer to write it but I'm not really a > DB/ORM expert having only used Hibernate/EJB-3.0 for a few years with > mysql. I don't really have that kind of time either. > > Long and short: Go with SA if it looks robust and has good docs.
On another note however, I really don't think having the options in gears is a bad thing, even if it does add a level of complexity to the documentation and to learning. What attracts me to gears over other platforms is that fewer decisions are forced on me in regards to how sophisticated different elements of the stack need to be. In the long run, this is good because web dev is woefully inconsistent. Sometimes I will get clients who's db needs are totally minimal and SO will be a better fit, sometimes the opposite. I do not think most serious web developers who come to gears want to be told that this particular component is always the best solution, because we know otherwise, and when a components sophistication is overkill, that just slows down development. Personally I'm willing to take longer to wade through docs to have a varied tool set. If you only have one chisel, it's easy to pick your chisel and learn how to use it. Doesn't mean it's good to only have one chisel. ; ) Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
