Hi! I have read this thread, and it made me a little bit sad, as Alberto and I have invested much energy into RUM.
I recognize, that every impression about the project is posted by the best knowledge. Nevertheless, I find the information here rather misleading. So please, let me clarify some things. - performance: I think the current versions are maybe not fast as a Porsche, but fast enough for most purposes. We had some heavy problems until the beginning of this year in tw.rum. These are fixed now. The last performance issues, I had were due to SA/Genshi (when using much data). Moreover, I want do denote, that due to generic functions, it is fully possible to extend our query mechanism for eager loading related objects. This can speed up index views even more. In this way, this demonstrates, that the generic design in RUM is suited to make good use of the underlying excellent SA technology and can be used as way, to avoid performance penalties of abstraction. - bugs: please feel free, to report every bug to our mailing list or trac instance. We take issues very serious. In fact, Alberto and I were the first, who stepped in, when there were heavy security issues in TG2 (in no way a problem *in* RUM), which were reported on our mailing list. This demonstrates, that we take care. Of course, we completely can't avoid bugs, but we do our best, to take issues serious. Personally, I use a RUM instance on a production application with much content, which is edited by real end users (those, who make your phone ring, if something doesn't work). ------ What is still missing are some nice Ajax widgets. Anyways, meanwhile we have plenty of features: Come in and explore! On 20 Apr., 04:13, Agustin Villena <[email protected]> wrote: > I noticed that Rum & DBSprockets were left nehind and now the prefered > CRUD solutions is Sprox (http://sprox.org/) There was some consense in the TG2 community, that TG2 should work on IronPython/Jython, the use of peak.rules in RUM has been seen as problem for portability to other Python versions. I think, the Pylons community has a very good understanding, that there can exist different components for the same purpose with their own advantages. Michael --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
