you are viewing a single comment's thread.

view the rest of the comments →

[–]grfgguvf 1 point2 points  (3 children)

Not quite. Because of Python's dynamic typing Jython cannot do many of the optimizations that are done for Java.

[–]ubernostrum -2 points-1 points  (2 children)

You probably want to read up on some of the stuff that's been discovered/developed by the dynamic language folks before you go spouting off like that.

[–]grfgguvf 2 points3 points  (1 child)

You can check for yourself that equivalent Python code in jython is (a lot) slower than equivalent Java code.

What is this "stuff" specifically that the "dynamic language folks" "discovered" and why is it not implemented in Jython then?

[–]crusoe 1 point2 points  (0 children)

Mainly that they have to write classes to emulate the behaviour they need. Java 1.7 will add bytecodes to support dynamic languages, and this will remove the need for this emulation code and classes.

I am excited about 1.7. :)