Ray wrote:
> Does the comparison between dynamic and static language carry over to
> comparison between Django and Turbogear too? Is this what is meant by
> "Turbogear is much more flexible than Django"?
Nah, the difference is more than Django is a complete product whereas
TurboGears is a collecti
Fredrik Lundh wrote:
> I hope you're aware that this sounds a lot like late 90's anti-dynamic-
> language propaganda...
>
> "I would never use Perl or Python over C++ for any performance-
> "intensive Web app. In my opinion, both languages make some
> poor design decisions regarding th
Adrian Holovaty wrote:
> I would never use TurboGears or Ruby on Rails over Django for any
> performance-intensive Web app. In my opinion, both frameworks make some
> poor design decisions regarding the importance of performance.
I hope you're aware that this sounds a lot like late 90's anti-dyna
bruno at modulix wrote:
> Possibly - but if a programmer is not able to pick on Python in a matter
> of days, then it's a bad programmer that won't be of any help whatever
> the language. So in fact, choosing Python may help you get better
> programmers !-)
You have a point there! :)
> You may a
Very useful input, Adrian.
Thanks a lot! These are facts that I can use to convince people that
Python is a legit choice for the app I'm developing.
Warm regards,
Ray
Adrian Holovaty wrote:
> Ray wrote:
> > Yes, but this is more of a web application though--something that I've
> > never develop
In article <[EMAIL PROTECTED]>,
Tim N. van der Leeuw <[EMAIL PROTECTED]> wrote:
>
>- Do you have to interface with things like messaging-systems (a la JMS
>specs), distributed transaction managers? If so, the only way to go
>Python is Jython: Python for the JVM. Because AFAIK, there are no
>interfa
Ray wrote:
> Yes, but this is more of a web application though--something that I've
> never developed in Python before, so... I'll be evaluating Django
> shortly--let me see how it compares to Tomcat.
Performance is one of the key features of Django. For example, I'm
using Django at washingtonpost
Ray wrote:
(snip)
> But then on the other hand, there is a manpower problem--it's damn easy
> to find a Java programmer (although the quality that you get is a
> different matter). Python programmers are more difficult.
Possibly - but if a programmer is not able to pick on Python in a matter
of d
Tim N. van der Leeuw wrote:
> Hi Ray,
Hi Tim!
> I'm in a bit of the same boat as you only I don't get to choose my
> implementation language ;-)
>
> Some of the concerns should be:
> - Do you have to interface with things like messaging-systems (a la JMS
> specs), distributed transaction manager
Hi Ed,
Ed Singleton wrote:
> Personally I have found that if you need to sell a technology on,
> saying it's written in Java is an advantage generally (because "it's a
> standard"). If it's written in Python you may get asked why it has
> been written in a "scripting language" if they've heard of
On 11 Jan 2006 17:54:05 -0800, Ray <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I've got the chance to determine the technology to use in creating a
> product similar to this:
>
> http://www.atomicisland.com/
>
> Now the thing is that I need to sell this to the guy with the money.
> I've developed for y
Hi Ray,
I'm in a bit of the same boat as you only I don't get to choose my
implementation language ;-)
Some of the concerns should be:
- Do you have to interface with things like messaging-systems (a la JMS
specs), distributed transaction managers? If so, the only way to go
Python is Jython: Pyth
Hello,
I've got the chance to determine the technology to use in creating a
product similar to this:
http://www.atomicisland.com/
Now the thing is that I need to sell this to the guy with the money.
I've developed for years with C++ and Java, last 7 years J2EE, and I'm
kinda sick of the "bloated
13 matches
Mail list logo