Interesting. I wonder how well that has worked out in practice.
Seems to me like any designer smart enough to get comfortable with Django's templating language probably wouldn't have any trouble getting comfortable with Python itself!
It's not like you'd ever do anything particularly complicated (programming wise) from within your templates anyway.
b. ATC systems often use languages that pre-date Ada.
c. The point remains - often the technical people don't get the choice of language. This is the most relevant point when you put this in the context of the discussion from which it branched.
Not _quite_ to the point of absurdity. I kinda like it. Admittedly, I dislike it when I have to instantiate four classes to read the contents of a file. But I have also used the same flexibility to great advantage, and been burned in other languages when the standard library wasn't flexible enough.
Err, I think the Cliq is actually a totally different phone for T-mobile but with a similar form factor. The hardware on the Droid is much better, eg. 848x480 screen instead of 480x320 screen. I don't think the Cliq has an OMAP SoC either, probably ARM11. And the Droid uses stock Android 2.0, whereas the Cliq has Android 1.6 or 1.5 with Motorola's MOTOBLUR on top. But the Droid will have wifi, since it's a higher end model, and Verizon has changed its policy of removing wifi now that they require data plans on smartphones anyway.
