Re: Giving up PHP. ...Can't decide between Django & Rails

I came from java (spring mostly) then asp.net then php, rails and finally to django. While django is my favorite I can still use all the others just fine. Don't box yourself in and become a zealot of any one language/framework. Learn many and keep exploring. It will only make you a better

Re: Giving up PHP. ...Can't decide between Django & Rails

Grok + zope3 could be a choice too. On Sat, Apr 17, 2010 at 05:39, hcarvalhoalves wrote: > Why do you have to "make a choice"? Learn both. They can be useful in > many different ways. > > I learned Rails (and Ruby) before Django, because I saw some material > for Ruby

Re: Giving up PHP. ...Can't decide between Django & Rails

Why do you have to "make a choice"? Learn both. They can be useful in many different ways. I learned Rails (and Ruby) before Django, because I saw some material for Ruby that got me interested in hacking on it. Some time later, Rails got really popular. Then lately I learned Python and Django,

Re: Giving up PHP. ...Can't decide between Django & Rails

Hi everyone, one thing I would take into consideration, when evaluating languages/frameworks is the community. And I cannot stop being amazed at the Python/Django people. I mean just look at this thread: Someone comes in with a (serious) question, that would usually end in flamebait and religious

Re: Giving up PHP. ...Can't decide between Django & Rails

I came from a job where I had been crafting applications using zend framework - probably the closest thing php has to django. The more object oriented my php code became, the more it looked, and smelled, like java. I ended up taking a new job, where my projects started to have dependencies on

Re: Giving up PHP. ...Can't decide between Django & Rails

Hiii I personally love working in Djngo as compare to Ruby. First of all Django is having great Admin part with customization and all. and working with it is really a great fun. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this

Re: Giving up PHP. ...Can't decide between Django & Rails

On 9 avr, 18:06, UnclaimedBaggage wrote: > > 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? Not enough experience with

Re: Giving up PHP. ...Can't decide between Django & Rails

I went with Django because of Python. It is a multi-purpose language that is used in the sciences, social sciences, and scripting for software\videogames. Ruby on the other hand is primarily known just for Rails. I also figured Python would be faster and only get faster due to Google's Unladen

Re: Giving up PHP. ...Can't decide between Django & Rails

Hi, > I'm a little concerned by django error handling. you could try the Werkzeug debugger[1], it really does save time a lot. Or, by the way, you could try Werkzeug without Django, in some cases it's a good idea. There are many good frameworks, I suggest that you pick the language first and

Re: Giving up PHP. ...Can't decide between Django & Rails

This is a tough question for sure. If you prefer Ruby syntax, then to me it seems clear. If it feels clunky, it won't flow properly and you won't code as well. Then again, you point out that you built a finished product quickly and you're happy with it compared to what you built with Rails.

Re: Giving up PHP. ...Can't decide between Django & Rails

On 9 Apr 2010, at 18:13 , UnclaimedBaggage wrote: > > 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

Re: Giving up PHP. ...Can't decide between Django & Rails

Hallöchen! Wiiboy writes: > [...] > > 2. Regarding documentation, the docs at > http://docs.djangoproject.com are, in my opinion, simply amazing. > By far the best documentation for a free project that I've seen > (but then again, I haven't seen much). [...] They are great. Really great. And

Re: Giving up PHP. ...Can't decide between Django & Rails

I'm a bit of a noob as well, and know nothing about Rails, but I'd like to comment on a few issues you mentioned. 1. Non-existent template variables are replaced with the value of the TEMPLATE_STRING_IF_INVALID setting. Set that to something besides its default (an empty string) to make

Re: Giving up PHP. ...Can't decide between Django & Rails

I think it largely boils down (as many have said) to a python vs ruby debate. I personally hate Ruby... I think its perl with a nice syntax, its very obtuse and just downright hard to maintain as projects get bigger (IMHO, others I;m sure disagree). As far was what is better about Django for

Re: Giving up PHP. ...Can't decide between Django & Rails

On Fri, Apr 9, 2010 at 11:13 AM, UnclaimedBaggage wrote: > 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

Re: Giving up PHP. ...Can't decide between Django & Rails

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

Giving up PHP. ...Can't decide between Django & Rails

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