| Article: |
Introduction to PyObjC | |
| Subject: | Java... | |
| Date: | 2003-02-04 05:16:55 | |
| From: | anonymous2 | |
|
Does this have any bearing on using Jython (possibly taking advantage of the Java bridge for Cocoa)? |
||
Showing messages 1 through 1 of 1.
| Article: |
Introduction to PyObjC | |
| Subject: | Java... | |
| Date: | 2003-02-04 05:16:55 | |
| From: | anonymous2 | |
|
Does this have any bearing on using Jython (possibly taking advantage of the Java bridge for Cocoa)? |
||
Showing messages 1 through 1 of 1.
However, outside of the novelty of such an achievement, I could imagine why one would want to do so!
In general terms, the PyObjC bridge-- though still in need of refinement-- provides a more natural/transparent bridge between the two target languages than does the Java bridge.
This is not criticism of the Java bridge, but the simple reality of Java itself. The Java language-- the Java VM-- tends to be a very "active" environment. It requires full and complete control over the runtime environment.
Python and Objective-C tend to be somewhat "passive" in nature. Neither demands complete control and both offer tremendous opportunities for integration with and extension of the basic language/runtime.
As such, integrating the two is a very natural fit.