Should I use Django on Jython?

Someone posted a quick question on the NextNY list today more or less asking if using Django on Jython made sense…for whatever reason, I dumped a fairly long rambling response…and I liked my points well enough that I’m cheesing out tonight and using that as my post of the day as well! Read on to see what my thoughts on the subject were…

Django is very popular right now…however I don’t know that Django on Jython is as popular or hot.

My personal opinion, if you want to have the ‘advantages of Java’, then use a java framework…there are a ton of solid Java frameworks that allow for rapid development and that have a large core of available developers.

There are actually two discussions you have here though - one is on language and one is on framework.

Rails, Django, PHPCake, Groovy, Catalyst, .NET, etc….these are all just frameworks (and most languages have a version of each framework)…frameworks are about the technical design of your application…how things are laid out and how they are going to interact. Organization if you will. They come into play with ease and speed of development, but really it’s about the design of how you want things to work (how you want to think). Each developer has a preference or a way of thinking that fits best with them, and so each developer will have a framework that they find easier (or harder) to work within…but again, just about every language has a version of the general framework patterns you can use…

The other question you have in here is about language…and to me this is the bigger question to start with. Do you want to use PHP, Ruby, Java, Python, C#, Coldfusion, Perl…I believe you should make this decision first, and then pick the framework within that language you like the best.

Of course there are lots of pros and cons to each language…and every developer feels strongly about their language of choice…the reality is that most any of them are going to be a fine choice…if you’ve got the budget, you can find developers in any language…

But budget is an important point, languages like PHP are def. cheaper to find developers in than say Java…but that doesn’t mean you are going to find the right PHP people…it just means it’s a little easier to learn, and so you can be a bad developer who can make things sort of work faster/easier than you can in another language…and it goes in all directions…a top notch PHP guy can code something better/faster/strong with or without a framework than a newbie Ruby programmer doing Rails could…but a newbie Ruby on Rails guy *should* build a better system faster than a newbie PHPCake guy…

You see the thing a lot of the marketing or buzz or language/framework wars don’t really mention is that, the war is really over the newbie…what language/framework can you go from 0 to 60 with the fastest and easiest…but when you start talking about real projects and real companies…you probably don’t want to go from 0 to 60, you want to go from 60 to 100…you want developers that already know what they are doing, who know the language they are going to be working in, who have some experience building the types of systems (or at least parts) you are looking for…and when that’s the case, whatever language/framework they already know is the 'smartest’ decision for your project.

This post has received 50 loves.


This is the personal blog of Kevin Marshall (a.k.a Falicon) where he often digs into side projects he's working on for and other random thoughts he's got on his mind.

Kevin has a day job as CTO of Veritonic and is spending nights & weekends hacking on Share Game Tape. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at

If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).