Slashdot Mirror


Sun and Eclipse Squabble

gbjbaanb writes "CNET news is reporting on a potential spat between Sun and Eclipse: 'Sun Microsystems has sent a letter to members of Eclipse, urging the increasingly influential open-source project to unify rather than fragment the Java-based development tool market.' Although Sun's letter says it wants interoperability, and a 'broad base' for java tools, it then insists Eclipse should push to be a 'unifying force for Java technology'. Competing tools is a good thing, but it sounds like Sun just wants everything to work its way."

11 of 423 comments (clear)

  1. Eclipse will take out Sun by Anonymous Coward · · Score: 5, Funny

    But it will be short-lived... maybe only a few minutes. Then Sun will be back.

  2. let's see sun invents java, ibm, makes a tool ... by ikeee · · Score: 5, Insightful

    Who in the sane mind would ask such a thing... Come on, wasn't java supposed to be write once run everywhere..., So how on earth multiple IDEs are going to cause problem...

  3. Re:A lesson from Microsoft by AKAImBatman · · Score: 5, Interesting

    You don't know what you're talking about. Sun gives away Forte for Java under an Open Source branding (think Mozilla/Netscape). The real reasons for this squabble go back to '01 when IBM released Eclipse after inviting every company except Sun to join the project. At the time, Netbeans/Forte was very mature and would have been a good choice for IBM to build their own platform off of. Instead, they named their product as a way of snubbing Sun, and used their own proprietary GUI API so the two projects could never interoperate.

  4. I don't think it's so nefarious. by sQuEeDeN · · Score: 5, Insightful

    I don't think it's as bad as the poster implies. Let's look at the facts:

    1: Sun develops Java. We all owe them for that. Let's face it. Love it or hate it, Sun has created a widely used language. They control what goes into the language.

    2: Eclipse, as a development platform, is gaining ground all the time. Great. I'm all for diversity.

    But, Sun's position is understandable. The presence of programming tools, in this corporate climate, can make or break a language. It seems like sun, more or less, is looking to have a more formal place in Eclipse's management. Conspiracy theories, of course, are abound.... except,
    JAVA IS SUN'S LANGUAGE. Imagine, if Sun had more a voice in eclipse development, think of what is possible!!! What a concept? The language developers and the IDE developers working togeter?

    Sorry for my smart-assed comments. What my point is, this has just as much potential to be a good thing for Eclipse. Sun is certainly capable of providing constructive agreement, and the Eclipse foundation doesn't actually need to listen to Sun. I just think that there's a lot of potential for cooperation.

    --

    Recursive (adj.): see 'Recursive'
  5. Eclipse invited Sun... by The+boojum · · Score: 5, Interesting

    I find this interesting, considering that, not too long ago, the Eclipse consortium offered to join with Sun (and even change to a less threatening name if need be). Sun however, turned them down.

    Personally, I like the direction that Eclipse is going. I tried Forte once and it just didn't feel right. Eclipse however, has been fantastic since I found it and started using it as my work IDE. (My whole project team adopted it as well.) It has made coding Java a pleasure as no other IDE (in any language) has, and has led to me using Java as a development language for personal projects where I otherwise would have used C or C++. I've largely given over using XEmacs for coding Java. I'm also impressed by the speed of the Eclipse development cycle with new milestones coming out approximately every month. I always get this kid-in-the-candy-shop feeling checking out the New and Noteworthy page with each new milestone.

  6. Oh, well. Another pointless PR ping-pong match. by crazyphilman · · Score: 5, Funny

    Sun (to Eclipse): Hey, knock that crap off!

    Eclipse (with exaggerated innocence): Moi? Whatever do you mean?

    Sun: You know.

    Eclipse: Actually, no, I don't.

    Sun: Don't be coy!

    Eclipse: YAWN. Do you have something to say or what?

    Sun: You know damn well we're working on Swing, and Netbeans, and all that, and here you come out with SWT and start going off on weird tangents, I mean, hell, who's in charge here? I thought you were going to be cool about this.

    Eclipse: I am. People really dig java, and they're having a blast using Eclipse to work on it.

    Sun: Yeah, thanks a lot, poor Forte...

    Eclipse: I didn't tell you to charge so much for it.

    Sun: I didn't tell you to be free!

    Eclipse: No, that was my idea. But it's cool anyway. Anyway, you've got problems of your own. It's like, make up your mind already.

    Sun: What the hell are you talking about???

    Eclipse: Java 1.1.8, then Java 1.2, then Java 1.3, then 1.4, and every five minutes you "depreciate" something, driving your developers nuts...

    Sun: You... How can you... You...

    Eclipse: And then there's AWT, no, it's Swing, no, it's going to be some kind of weird beany scheme...

    Sun: You... OOOOH you make me SO MAD! Swing was a good idea! So were the beans!

    Eclipse: Well, so's SWT. Deal.

    Sun: It's not the same thing!

    Eclipse: Sure it is.

    Sun: Is not!

    Eclipse: Is too!

    Sun: Is not!

    Eclipse: Is too! Anyway, what's the difference? SWT is based on AWT, so it works everywhere, doesn't it? You should really dig it.

    Sun: (Sulks)

    Eclipse: Aw, come on, join the board of directors. You know you want to. You can even keep your Netbeans. I promise.

    Sun: I'll think about it...

    Eclipse: Yep. I know.

    --
    Farewell! It's been a fine buncha years!
  7. Re:Competition will be better in the long run... by Anonymous Coward · · Score: 5, Insightful

    I think people are missing the point. Java is all about interoperability. Look at J2SE and J2EE platforms... code that is written to a spec can be deployed on any vendor's application server that adheres to that spec... ect. So, why should Java development tools still be proprietary? Thats what Sun is saying. Lets agree on specs like everything else we do. If Joe Hotdog writes a neat plugin for eclipse, it should work in all the other IDE's too. Nobody gives Sun credit for creating a great language and most importantly an open, competitive market.

  8. Re:Java... by Mysteray · · Score: 5, Interesting
    Gnuman99:
    Maybe if Sun actually released the source to Java under a free license, maybe, just maybe, people might improve it and use it.
    Khakionion:
    After all, they want to force people into their way of thinking now, why would they accept any changes to Java that someone made that didn't mesh with Sun's current plan for the growth of Java?

    They wouldn't have to accept any changes they didn't like. They could still enforce exactly what they wanted with the Java trademark. They could put the source in the public domain with the simple stipulation that non-strictly-compliant implementations couldn't be called Java(tm).

    Not having it free software certainly didn't slow Microsoft down one bit from extending it without their approval. In fact, the result was a freshly-designed competitor (C#/.Net).

    They don't even seem to be making a profit on the language itself, why this obsessive desire to control it with an iron fist?

    As for the people-might-use-it question, it would certainly make all the difference to this developer. I know there are free Java implementations, but until I see a solid crossplatform GUI kit, I'll probably continue to look elsewhere.

  9. User Interface by c_waddington · · Score: 5, Insightful

    Is it all about Swing vs AWT? I hope not. I think Eclipse is great! But Eclipse got it right and Sun got it wrong. I want my user interface to look like the operating system I'm using (not Java L&F) and I want it to be natively quick. Please compromise Sun - The native approach is better as long as the toolkit can always guarantee to draw the lowest common denominator. That's what Java should be - write once, run everywhere, to the best of individual platforms abilities.

  10. Eclipse Forte by agwis · · Score: 5, Informative

    I've tried the 2 of them and they both are pretty decent IMHO. The big difference, and I mean big, is how responsive each are on a fairly moderate system. After starting forte, I can go have a coffee and a smoke and maybe even take a quick nap...at which point forte should be running when I get back and I can then get to work.

    Eclipse on the other hand is really fast. When I first tried it I couldn't believe that it was a Java program. It even looks good, rather than that ancient, dull look that most Java apps have.

    Since then, I've upgraded to a P4 with 1G ram and they both run pretty good (although Eclipse is still much faster). I do like both of them but Sun and IBM and anyone else interested in furthering Java should collaborate on 1 killer IDE that puts any MS tools to shame, and allows lazy programmers (like me!) to be more productive in less time :) As Eclipse appears superior to forte and probably has the largest installed base (don't know how it compares to Jbuilder) Sun would probably get a lot more respect from developers.

    -Pat

  11. Re:A lesson from Microsoft by kfg · · Score: 5, Funny

    Sun and IBM are competing rivals. Nothing more ugly than that. It's a credit to Sun than IBM should name their work in such a way.

    Indeed. Sun should feel honored to have such a noble and gallant competeing rival pissing on its shoes in public.

    KFG