Ooops - forgot one other thing: I'm a little concerned by django error handling. The tracer stack seems to miss the relevant file a lot of the time, and I often find little help from the error pages even when it does get the right page (eg an error comes up with a useful file/line # in the debug page, but the cause is on another page and I'm struggling for indications as to where the bad code actually came from). This could, of course, just be my inexperience with the language, but do more experienced developers regularly find themselves having to "guess and hunt" exceptions/ errors?
Secondly, typoed template variables don't seem to throw exceptions. Is there a way of changing this? I haven't seen much in the way of getters/setters in example code, and I'm concerned that may make typoed variable/list/dictionary declarations more difficult to hunt down. Cheers again. ;-) On Apr 9, 9:06 pm, UnclaimedBaggage <baynej...@gmail.com> wrote: > Hi folks, > > I'm a long-term (8 years) PHP developer who's recently started > dabbling with Rails & Django. I REALLY like what I've seen from both > frameworks and quite frankly, am a little miffed I didn't jump on the > bandwagon earlier. > > I'm trying to decide between the two frameworks, but I'm > struggling to get out of stalemate. If anyone can offer advice, I'd be > very appreciative. Here are my current thoughts: > > WHAT I LIKE ABOUT DJANGO > * I LOVE django-admin . For the sort of work I do, which is a lot of > customised cart/cms stuff, this would save a lot of time. > * Code reusability seems superior. Opinions? > * Better perfomance? > * I've half-built a shopping cart app in Django that I'm happy with. A > quick dabble in Rails made this task seem a little more time- > consuming, and I'm not comfortable with drop-in solutions > * Server seems more stable. Using the rails dev server on a local > linux box twice threw errors I couldn't trace, then worked fine again > the next time I restarted my computer (having previously restarted the > server with no result). Is this a common problem? > > WHAT I LIKE ABOUT RAILS > * I prefer the syntax > * There seems to be a lot more work for rails...with better pay > * "Agile Rails" is a damn fantastic book. I haven't found much Django > documentation I've enjoyed as much > * Seems to be a little simpler > * Seems to have a greater depth of features > * Better AJAX integration from what I've seen > > Obviously I expect some django-tilted opinions here, but if anyone > with > experience in both can offer a balanced perspective on pros-n-cons of > each it would be a big help. > > Cheers. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
