Hacker News Reader

Comment by gte910h | Hacker News Reader

What happens when you do a django template "your way" or "they way we can do it in 2 hours instead of 12"? What happens with the same thing in a Rails project?

People may dislike that you did it, but you still CAN. That's the difference. With Ruby on Rails, you can't necessarily due it without the wheels coming off.

>I'd still go python over ruby, cause I'll take libraries

This is a comment about the non-web components of the language.

>how is Django not dramatically more opinionated?

The Django community is perhaps more opinionated. The actual software isn't. That's the issue with Rails. The actual software has strong opinions (aka, intentional inflexibility) baked into it. I honestly wouldn't pick Django either (preferring even less strict frameworks), but the OP asked a question X or Y, and I told him of those two I feel is better.

View on HN

    What happens when you do a django template "your way" 
    or "they way we can do it in 2 hours instead of 12"?

I've worked on a lot of projects and can't imagine the situation where you'd have this kind of a variation in time to create two remotely similar versions of a template. If you are talking about a fully designed template + CSS + JS, then you could possibly get up to 12 hours, but there would be no way to shorten that to 2 hours without doing something completely different.

    This is a comment about the non-web components of the 
    language.

And this entire discussion is about web development. The OP, who already knows multiple non-web-centric languages, asked specifically about web frameworks.

    The Django community is perhaps more opinionated. The 
    actual software isn't.

Depends on what you mean by the software. The framework overall is very opinionated, even if you can use parts of it in a modular way.

    The actual software has strong opinions (aka, 
    intentional inflexibility)

Let me take the opportunity to give you a heads up that Rails 3 has been out for months now and is widely used in production. One of the most significant design goals of Rails 3 was intentional flexibility.

You're thinking web apps. Think "apps that have some views which are to the web, but most data feeds for other services" and you'll be in the zone were in. Json and Xml feeds and the like.

>Depends on what you mean by the software. The framework overall is very opinionated, even if you can use parts of it in a modular way.

Also, Django is WSGI. WSGI is very easy to add layers to to get the job done. (Side note, does everyone pronounce that Wizz Gee in your part of town? They sure as hell do in Atlanta and it slightly confuses me every time I hear it in conversation but can't figure out they're saying WSGI).

Reply on news.ycombinator.com