Python
App Engine kind of rocks if you use the Python version. The JVM version, which is what you're stuck with if you want to use Ruby, isn't even good enough to suck. It isn't even "beta" or "testing". It's a complete joke. It takes 13-20 seconds to warm up, and it cools down after a few minutes of not being used. That renders it completely useless
( Read more... )
There's a pretty good argument to make that requiring explicit 'self' in the parameter list reinforces the theoretical equivalency between these two ways of calling a method, given that 'foo' is an instance of 'C':
foo.meth(arg) == C.meth(foo, arg)
It's neat to know that that's how it works, but unless I'm missing something, his argument has nothing to it. Under the hood, methods are invoked with Class.method(object, argument), but we're allowed a little syntactic sugar, so that we can normally invoke them with object.method(argument). If he's willing to do that, the question remains: why isn't he willing to let
Class C
def method(argument): pass
just be syntactic sugar for what under the hood is interpreted as a method that takes two arguments, the first of which normally gets passed automatically, but which you can still do manually with the Class.method(object, argument) form if you want/need to?
Reply
Leave a comment