On Jun 30, 4:22 pm, Casper Bang <[email protected]> wrote: > > Isn't it slightly underhanded to conflate JNI with GUI design? After all, > > it's only swing that actively tries to avoid any native functionality. > > That's an analogy made by you though. The philosophy is apparent > throughout the Java language itself, Swing is after all just a > library. My frame of reference would be C#, where you can import a > libc method with a single line of code,
You can in Java too, with JNA. > call into Visual Basic, Python, Ruby etc. well except for Visual Basic, of course, we have Jython, JRuby, Rhino etc. and a standard API to talk to them (JSR-223, which is not optimal, but at least it's there). Embracing the underlying platform means much more than interfacing with C. It means following certain conventions (e.g. where to put stuff in the file system), playing nice with the rest of the platform, etc. but also being tied to that platform. Java has chosen a certain trade-off; the JVM is not a typical Unix application nor a typical Windows application. In that vein it's similar to most Lisp or Smalltalk implementations, that build a sort of closed universe with its rules and few contact points with the outside world. The "scripting language" philosophy it at the other end of the spectrum; it makes certain things easier and other things harder. -- You received this message because you are subscribed to the Google Groups "The Java Posse" 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/javaposse?hl=en.
