We need PIGs :)
stefan.arentz at gmail.com
Thu Sep 6 09:00:02 CEST 2007
Bruno Desthuilliers <bdesth.quelquechose at free.quelquepart.fr> writes:
> The problem with Java is that it makes it very painfull to bridge two
> APIs together, while Python usually makes it a breeze (easy
> delegation, no dumb-ass psycho-rigid type system). So Java's solution
> (hyper-formalization) isn't necessary here.
Interesting. I find Java much more predictable with APIs than Python
actually. Java has pretty strict rules for style and API design, which
basically all modern code follows pretty well. I think this is mostly
the result of a strict JSR regime.
What I find really frustrating in Python (combined with usually bad
documentation) is that many people have different styles. The most
frustratinng being getFoo() vs .foo, vs get_foo().
More information about the Python-list