The advantages that you cite for Rails are exactly what frustrates me here. Rails has a humongous, fanatical, user base. So many podcasts, screencasts, books, blogs, sites, etc.. etc... Its marketed as well as Budweiser Beer, for sure. Spuds McKenzie never made that crap taste any better though. I agree, 80-20, Rails is fast. Its as fast and versitle (though arguably not very scalable) due to its fanatic user base. There's gems for everything out there and generators as well. Now, Pylons and TurboGears, lack in documentation (it seems you really have to get a book, unfortunetly), and you may find yourself creating some things that you were accustomed to in Rails. I haven't yet found a good source of Paste scripts out there (to rival generators in Rails), though its pretty easy to write your own. The Python Package Index (PyPI) does have some things on there though no where near the amount of gems. Though the biggest item to argue in favor of the Python platform is Python. Everything is indeed way decoupled. You can have any ORM you want (Rails 3 only now offers a different ORM) or any templating language. You will find that you can also look under the hood and McGyver things allot easier then you could with Rails. There is no DSL here, everything is pure sweet, simple Python. Its like trying to fix a Honda (Rails) vs. a VW (Python platform framework). One thing that I'll miss is Cucumber... Saw somewhere that it isn't really feasible with Python due to the lack of real "introspection" in the language. Though it seems like, the somewhat recently introduced, decorators would work. I think you will like the web debugger (I know, small things).. it has an ajax shell allowing you to run code right there, plus you can automatically search the exception on the web or submit it to the forum... pretty neat.
On Jul 28, 9:21 pm, Guyren G Howe <[email protected]> wrote: > On Jul 27, 2010, at 12:33 , waugust wrote: > > > So, I divert the topic from technical questions to this rant to ask > > you: Why and how is it possible for the industry to allow us to > > degrade the progress of technology in favor of good marketing? > > As a long-time Rails user and new TurboGears user, let me make some comments > in Rails' favor, and to compare and contrast what I've seen of TurboGears so > far. > > First: it is much easier to get into Rails because there is an order of > magnitude (maybe two) of documentation, much of it of very high standard. The > documentation that there is for TurboGears is of quite good standard, but > there isn't enough of it, and much of it is out of date or incomplete. > > Second: you are selling Rails rather short. I can't say yet whether > TurboGears is better, but Rails is very good. And Rails v3 in particular is a > very solid and mature product. I can get shit done in Rails 3 very quickly, > and what I write is concise, readable and easy to maintain. > > Ruby and Python are both, I think, equally good languages for different > reasons. Most developers I know who have spent time with both find both quite > comfortable and effective languages. This is certainly my opinion. > > From what I've seen, TurboGears is a much more loosely coupled design than is > Rails (although Rails 3 is now similarly loose), which I like. And I like the > batteries that are included, particularly ToscaWidgets. > > As I say, I'm not familiar enough with TurboGears to offer an opinion about > which is better. But I think that even if TurboGears is better, it cannot be > by as much as you suggest. Rails really is very good. -- 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.
