[email protected] wrote: > Is this correct? In my limited understanding of web frameworks....it > seems the world started out with difficult to learn options like Zope, > J2EE and ASP. > > Then if I'm not mistaken, Ruby on Rails came up with some innovative > ideas to make things easier that TG, Django and other frameworks > borrowed heavily from. >
No. They came up with marketing ;) > ....What are these innovative ideas that Rails came up > with that distinguishes TG/Django/Rails from Zope/J2EE/ASP that they > all have in common? > Oh well, you cannot compare them in equal terms. I know TG and Zope3 for instance, and I've chosen the former for the limited scale of my project. If I were to design something bigger, or were looking for a job and were proposed to work with Z3 with people that already know it, it could be worth to go back to it. TG or Rails or Django have no magic dust, they just make a lot of assumptions (RoR even more) that bigger frameworks don't. I discarded Django because its ORM was not flexible enough, for instance. Heck, I don't even know if Rails has support for compound primary keys yet, many applications would be horribly complicated by that. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
