I tolerate javascript. I am also tolerating python.

GTK is a huge gift from google because I have become too used to to
decipher problems from cryptic java compilation logs. Familiarity
breeds contempt - contempt for the ways others do their programming.
It's hard for me to work with scripting languages because I don't want
to memorise all the pitfalls to avoid. I want the compiler to tell me
that my syntax is wrong and depend as little as possible on tracing
the output of a debugger to verify my syntax. Debugging is for
verifying logic not syntax.

Programmers who are deeply involved in PHP, python or perl find it
difficult to empathize with the attitude of the java or c++ programmer
- precision of syntax and logic. It was a huge relieve to move away
from Perl into java. GTK provides a similarly huge relief for me to
code with as little javascript as possible. We don't want to muck
around with uncertainties.

Basing app engine on a derivative of java is better than continuing
the development on python. Use of python as the initial platform was a
smart choice - for a beta test-out of the app engine concept. But as
complexity of the product grows, it's time to base it on a language
that offers more precise behaviour.

Invariably, we write quick and dirty rapid developments in perl or
python with lots of javascript to show customers a working concept. As
soon as they like it, we quickly move it into java and gtk, rather
than depend on the imprecision and lack of discipline of scripting
languages and the huge amount of mental interest needed to debug and
maintain such scripts. To free us to focus on more complex issues such
as synchronicity and security.


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to