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 developer even if you only work professionally with one
stack, learning and playing with other things will open up your mind.
For me yes I love python and django but I also play with erlang, lua,
haskell, xyz framework... you name it. It's good for yer noggin.
-Steven Elliott Jr
On Apr 17, 2010, at 6:29 AM, Massimiliano della Rovere <massimiliano.dellarov...@gmail.com
> wrote:
Grok + zope3 could be a choice too.
On Sat, Apr 17, 2010 at 05:39, hcarvalhoalves <hcarvalhoal...@gmail.com
> 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 that got me interested in hacking on it. Some time later,
Rails got really popular. Then lately I learned Python and Django, and
I've been working with it professionally for 2 years now.
Now I don't have much more interest in Rails anymore, because Django
seems to cover all you can do with Rails, plus the benefits of Python
(you have a faster language, with more libraries and in a more mature
state). Syntax and all for more is close to irrelevant - what matters
is productivity. Some people will get you into religious wars about
blocks, or test driven frameworks, or whatever is the trend... skip
over those.
I would recommend learning other frameworks too. Python got a big
share of web frameworks, that have their own focus on a particular
structure - some can be better for REST APIs than Django, for example.
[1] Ruby also got other frameworks than Rails, but they shine a little
less.
Also, I would recommend you to learn *the language* first, and using
the framework to play with it. Make sure you don't use this mindset of
"I'm sick of PHP - let me find a magic framework", otherwise you won't
get much further the 15 minutes blog tutorials. Real web applications
will still require a lot of your own components and glue code for the
framework, in addition to your domain logic.
Having said that, Rails is quite limiting, but still a good choice.
[1] http://wiki.python.org/moin/WebFrameworks
On 9 abr, 13:06, 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
.
--
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
.
--
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.
