You do know that 'Java' is to 'JavaScript' as 'car' is to 'carpet'. The push for getting everyone into HTML 5 using Javascript and all of those technologies necessitates getting rid of the old ways.īy which you mean the JVM? It has nothing to do with "internet standards" ffs. I'd imagine this market is now so small that it's no longer worth bothering with. Apple has only continued to invest money in their JRE to help sell XServes running OS X Server and running WebObjects. The idea that Java would be one of the dominant languages for OS X development died five years ago. New Cocoa APIs were not added to the bridge.
This was deprecated some time around 10.2 or 10.3 (I can't remember - Wikipedia probably can), largely because no one was using it.
You could call the Cocoa APIs directly from Java programs with some low-level automatic translation letting you use Java strings and arrays instead of NSString and NSArray, for example. They also shipped an Objective-C to Java bridge.
#Flash not working on chrome for zomg mac
It also included a lot of stuff for native integration - you could make the menu bar sit at the top of the screen from Swing apps, just like a proper Mac App and use the standard Mac keyboard shortcuts, for example. For example, it shared classes between JVM instances, a feature that didn't appear in the Sun JRE for a few years. The Apple JRE had a number of enhancements over the stock one. When Steve returned to Apple, he planned to make Java a first-class citizen of OS X. NeXT jumped on the Java bandwagon early on, porting their flagship WebObjects framework from Objective-C to Java. In general, Swing app usability is damning enough that Apple can just leave well enough alone and their customers will want Cocoa apps or Swing apps that have been engineered to look and behave a lot like Cocoa apps anyway. Apparently the Mac Java developer community had enough of a clue to realize that using Cocoa is a great way to restrict your app to one platform and miss the whole point of using Java in the first place.Īpple's special JVM was really just a way of trying to sneak Java developers into Cocoa, but it never really worked, so at this point, it's probably in Apple's best interest to just provide a stock JVM so people who really want to use Java can and let Oracle worry about whether or not Swing apps look like Mac apps. But they have in the past provided a way of using Cocoa through Java. I bet Apple would be happy if those apps just never ran on OS X. I promise you Apple doesn't care if Swing applications look similar to Mac applications since they won't behave like Mac apps due to not running through Cocoa. Using Cocoa is what they're really after, technically speaking, because their real goal is for all Mac applications to use the same toolkit, look nice and behave like other Mac applications. Apple would rather all developers use Objective-C, but that's just a way of ensuring that developers use Cocoa.
Right, but Apple does ship versions of Python and Ruby that can access their Cocoa libraries.
0 kommentar(er)
