Will Apple be supporting Eclipse and SWT better in the future?

Marcello pointed out this Apple job posting for a Java Frameworks Engineer in the Eclipse-Mac Google group:

“We are interested in an energetic developer who can master our Java implementation (Java, Obj-C, C & C++) and contribute to making Mac OS X the best environment for Java development.

…You will quickly become a valuable member of the team responsible for the next generation implementation of the HI Frameworks for Java on Mac OS X.

…Responsibilities include portions of the implementation of the MacOS X Java SWT, AWT and Swing APIs…

…Required experience:
We are looking for 1 of these 4 types of people:

has developed core pieces of the Eclipse IDE and has strong knowledge of SWT and its implementation

(emphasis is mine)

As far as I know, the SWT implementation for OS X has been an Eclipse Foundation affair, with Andre leading the way. So it is nice to see Apple starting to adopt SWT as one of its own.

I think they’ve done a great job with the Swing on OS X implementation. I think its one of the better (maybe best) Swing implementations available.

4 Replies to “Will Apple be supporting Eclipse and SWT better in the future?”

  1. I wouldn’t put it past Apple. My best guess is that they control their own version of Java so that they can control exactly how AWT and Swing behave on Mac OS X. All of the rest of their Java could behave just like the other *nixes. It would make a lot of sense if they did the same for SWT. Apple joining the Eclipse Foundation would be a huge benefit to both parties.

    On the Eclipse side: I’ve used Apple’s dev environment and wasn’t overly impressed when compared with Eclipse. If Apple used Eclipse as a baseline IDE they would get a much better IDE with a larger user base (especially Java) with many available plugins, support for programming languages and feature updates for free from the open source world, which Apple seems to be embracing: Apache, Samba, BSD, etc. Apple could make plugins to support Objective-C in Eclipse.

    Why push Java over Objective-C? More people know Java and would be comfortable programming Mac OS X apps with it. More apps means that the whole platform is more valuable. More cross-platform SWT apps means that there are more apps that will work just as well on the Mac as they do on Windows, like Azureus. This leaves less excuses for people to switch to a Mac! Apple people making the Mac SWT port better would be great because there’s definitely a long way to go to match the Windows SWT port. Sure it works, but there are lots of things that aren’t hooked up yet.

    If Apple needs Eclipse developers maybe they’ll hire us, eh Luis? ;)

  2. For those of us who have tried and possibly failed, we know that developing java code under OS X and Xcode and other present tools, is not a pleasant experience and knowing this let me see if I understand this correctly: The Entire Apple organization is looking for ONE single Developer / Software Eng. to come and in do all that work and turn the entire environment to be hospitable and productive regarding java on OS X? Only ONE WHOLE Software Engineer? Talk about being cheap and expecting the impossible!

  3. We use Eclipse as our 3rd year Java IDE, and I run it on my Macintosh machines in preference to the Apple development environment. The students love it, especially the content assist and refactoring support–I’d like to see the same features extended to C++.

Comments are closed.