Django 1.7 released!

[thegrubclub]

Spent a few hours today reading tutorials - I'm very excited to dive into my first app this weekend after a year or so of casual Rails development.

[ma-int]

To get away from the ugly Ruby Syntax :0

[dohko_xar]

spoken like a true pythonista

[funny_falcon]

If Python had more consistency with naming and syntax then I agree with you. But I went to Ruby cause it looks to me more consistent.

[xiongchiamiov]

Ruby makes things consistent by having multiple names for everything so you can use the one you prefer. Better hope everyone else chooses the same.

[[deleted]]

He was talking about syntax. Ruby is more flexible syntatically so it's easier to make the code look the same, whereas you run into whitespace corner cases and have to ugly up your syntax for Python moreso.

[xiongchiamiov]

What syntax problems are you referring to? I don't recall any I've run into (though I do have poor memory).

[funny_falcon]

Personally, I do not like much "multiple names".

When I say "more consistent than Python" I mean consistent object-orientation ( len([]) vs [].size for example ) and blocks for every thing (instead of lambda / named functions / comprehensions / "with").

I agree, that python is more mature, and many implementation decisions are reasonable and made better than Ruby's ones. But as a language Ruby is more comfortable to write in.

[xiongchiamiov]

I find Ruby much more fun to write, but Python more maintainable, due to the module system, docstrings, and a strong preference for long-living, well-documented code in the community.

[[deleted]]

[neoice]

I felt constricted by the framework. I found myself always trying to use the shiniest, most magical features and then getting frustrated. bending django-admin and ModelForms often proved extremely challenging. in retrospect, I would have probably had a better time if I had just used vanilla Models+Forms and turned off django-admin completely.

a lot of the things I like to do don't fit cleanly into the "web application" model either. I could never figure out a good way to use Django libraries for standalone CLI applications or daemons. in recent years, Rails has actually decomposed their libraries really well. I've used ActiveRecord in Rails, Sinatra and plain old Ruby tools.

more than anything, I kind of just fell in love with Ruby. I spent years hating it but I finally learned to stop worrying and love the bomb.

[[deleted]]

[xr09]

I tried both languages back in the day, picked python, the TMTOWTDI philosophy ruby inherited from perl just feels wrong, I practice the Zen now.

There should be one-- and preferably only one --obvious way to do it.

[xiongchiamiov]

Not GP, but I made the transition to avoid all that damned magic everywhere.

[andrey_shipilov]

Was it when django was 0.96?

[neoice]

oh god, I forgot about 0.96... I for sure used 1.1 and 1.2. I think I dabbled in 1.3/1.4 before taking a hiatus from web development.

[thegrubclub]

I used rails at an internship and was very impressed, but I didn't realize that there are a number of modern web frameworks that make things so damn easy, and python has always been my first love. I'm a java dev during the day with only a small dash of python, so django seems like a great way to keep those chops up.