Slashdot Mirror


The Apache/Sun Relationship Worsens

d6y writes "Over on the O'Reilly weblogs there's an entry on the relationship between Sun's Java Community Process and Apache. Sun have been rubbing people up with wrong way (the problems of licensing open source J2EE containers; stuts v. JavaFaces; log4j v. JDK 1.4 logging....) and I hope this gets sorted out real soon. See also the original VNUNet article and Apache's position paper."

203 comments

  1. sun no like open src but not to open about it by Anonymous Coward · · Score: 0

    sun is being hit hard by linux,apache and other open src projects but is not so open about it

  2. Apache/Sun by Orville · · Score: 5, Informative
    A couple of thoughts:


    While it does matter in the aesthetic that Sun is restricting certification of open-source J2EE platforms, fortunately Sun has not taken drastic positions of 'shutting down' JBoss or anything like that. This letter from Marc Fleury seems to clarify the exact issue with JBoss.


    This seeming 'rivalry' between Sun & Apache is not as clear-cut; Many of the Jakarta contributors are Sun employees and engineers. (Tomcat/Catalina is used as the 'reference implementation' for the Servlet/JSP specifications.) For more on this, check out the former 'open source guy' at Sun: James Duncan Davidson

    1. Re:Apache/Sun by acroyear · · Score: 5, Informative

      Yes, many Jakarta contributors are from Sun, particularly with regard to Tomcat/Catalina. But many are not.

      Outside of Tomcat, IBM has been the biggest commercial vendor contributing to Apache, including core items Xerces, SOAP, and Log4J, and in each case Sun has refused to let Apache be the de facto standard (inspite of that being what i believe most java developers want), and has instead put out alternative APIs which its embedded with the JDK, thus locking everybody w/ 1.4 down to a standard that now has little room to grow.

      And in some cases the 1.4 bundled version is inferior to the Apache effort (yes, Crimson was/is better than Xerces 1.x because of IBM's redundant i18n overhead, but its NOT better than 2.0; and jdk1.4 logging is definitely not nearly as good as log4j).

      But as M$ has shown, people will stick with whats bundled, even if inferior, 'cause "its just easier that way"...

      ...& all java developers will suffer.

      Also, yes Tomcat is the "reference implementation" and all that, but that's because Sun has also released the code for watchdog, which is the standards-compliance testing tool for Servlets. What Apache and O'Reilly want to see is a similar effort to release the standards-compliance tests for other J2EE software specifications like EJB, and they consider it hypocritical for Sun to hold onto those tests in exchange for as much money as they charge for them.

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
    2. Re:Apache/Sun by bzzzt · · Score: 1

      But as M$ has shown, people will stick with whats bundled, even if inferior, 'cause "its just easier that way"...

      Which can be correct for consumer software, but we're talking about software developers now. If Xerces/Log4J are really that much better (read: save my time when developing) I will certainly take 5 minutes to download them.

    3. Re:Apache/Sun by acroyear · · Score: 5, Insightful

      the point is that if you are a new developer or program manager, working on a new project, and you see that the JDK tools already have an XML parser and a logging library, you're not going to even bother to look for alternatives.

      Just like nobody looks for alternatives to M$ Office or M$ IE, because its already bundled by OEMs onto just about every P4 box going out the door...

      its take developers of considerable experience, and influence over their manager / respect from their manager, to introduce tools to a development environment that on the surface seem redundant to the tools already at hand. right now, many of us have that experience, and the awareness of the better tools, but in a year that might not be the case...

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
    4. Re:Apache/Sun by IsleOfView · · Score: 2

      Sun has refused to let Apache be the de facto standard (inspite of that being what i believe most java developers want), and has instead put out alternative APIs which its embedded with the JDK, thus locking everybody w/ 1.4 down to a standard that now has little room to grow.

      Look -- nobody is locked down to anything. If develoeprs see more benefit in using Apache software packages for logging or xml parsing, there is nothing stopping them from packaging those along with their application and using them instead.

    5. Re:Apache/Sun by mark_lybarger · · Score: 3, Informative

      most certainly, and that goes for any platform/tool/whatever. every project of considerable size should have a compent senior engineer on staff to guide these types of things.

    6. Re:Apache/Sun by acroyear · · Score: 1

      well, duh...but you'd be surprised just how stupid and dilbert-like some companies and project teams can be...

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
    7. Re:Apache/Sun by mark_lybarger · · Score: 2

      sounds like a clear case of "you get what you pay for". i've been on a project like that, but it's pretty hard for amatures fsck up a Visual Basic database maintenance application development project :).

    8. Re:Apache/Sun by Anonymous Coward · · Score: 0

      The problem is that, for example, the JDK 1.4 logging looks more 'official' than Log4j (and I guess, in a way, it is). So people over at my company are all hesitant to use something that's not 'official'. I'd have to fight to use Log4j and the reality is that I have to spend my political capital on other, more basic things (like making our product not suck nearly so much).

      You know what? Concentrating on logging or whatever is actually making us ignore the real problem. The real problem is that the JCP is a scam. Do you realize how much money you actually have to pay to be part of the 'community'? And even after you pay, Sun just *ignores* the community.

      I'll say it again: the JCP is a scam. The J2EE license and certification process are both scams (Sun has admitted they do the certification only to generate revenue).

      Sun is crapping on its developer community and there is nothing I can do about it.

      Sincerely,
      Frustrated Senior Software Engineer

    9. Re:Apache/Sun by Anonymous Coward · · Score: 0

      Actually, you will, because you'll go to the Apache.org website, and see that Apache.org has all this Jakarta crap, and wonder what that is.

    10. Re:Apache/Sun by Anonymous Coward · · Score: 0
      But as M$ has shown, people will stick with whats bundled, even if inferior, 'cause "its just easier that way"...

      And what exactly is wrong with that? Jesus, you Apache people are a bunch of fucking cry babies. No one is forcing you to use anything here.

    11. Re:Apache/Sun by Anonymous Coward · · Score: 0

      Oh, and Xerces is a fucking pig in size last I checked compared to Crimson. I wouldn't want something that bloated as a de facto standard (crimson is much much better). Apache SOAP sucked hairy goat balls (maybe they can get it right with Axis, although I'm not holding my breath. Log4j... I don't need that complex an API to do my logging in 80-90% of the cases.

    12. Re:Apache/Sun by Kerg · · Score: 2
      the point is that if you are a new developer or program manager, working on a new project, and you see that the JDK tools already have an XML parser and a logging library, you're not going to even bother to look for alternatives.

      And why should you, if the supplied tools work well enough for your needs? If they don't work, you'll find an alternative implementation.

      its take developers of considerable experience, and influence over their manager / respect from their manager, to introduce tools to a development environment that on the surface seem redundant to the tools already at hand

      Hmm, if something doesn't work right, and your managers won't let you replace it with something that does work... ...

      I don't understand the point of view (that seems to be pretty common in Apache community) that there shouldn't be alternative options and that everything Apache does, and manages to create a reasonably active community of developers/users for, should be adopted as a de facto standard. This is similar to the attitude of people who argue that there should be, for example, only one open source J2EE implementation because having more "is a waste of resources". What does the Apache group have against having alternatives?

    13. Re:Apache/Sun by Kerg · · Score: 2
      ...& all java developers will suffer.

      Funny, I'm a Java developer and I don't feel I'm suffering. I'm competent enough to pick the tools I need by myself.

    14. Re:Apache/Sun by Anonymous Coward · · Score: 0
      Sun has admitted they do the certification only to generate revenue

      Damn them for trying to make a buck! They've created all this software framework and platform and are giving it away for free but its all useless cause to have a logo on your software you need to pay through your nose.

    15. Re:Apache/Sun by Anonymous Coward · · Score: 0
      Log4j... I don't need that complex an API to do my logging in 80-90% of the cases.

      What the hell are you talking about? It couldn't be easier.

      Category log = Category.getInstance( "foo" );
      log.warn( "something bad happened" );

      The only thing simpler is:

      System.err.println( "something bad happened" );

    16. Re:Apache/Sun by Anonymous Coward · · Score: 0
      Maybe you're just too stupid to understand...

      It's not a question of how I can get the equivalent of System.out.println the easiest. The Apache folks want the whole fucking framework to be used as a core component to the JDK. I don't need or want that BLOAT in my JDK, I don't need it in 95% of the cases. Log4j is alot bigger than one Category class.

      I find it hilarious that the log4j folks get so fricken upset when they're work is not deemed good for the JDK. LOL!!

    17. Re:Apache/Sun by ndfa · · Score: 2

      No sir, i believe what is really funny is how you are able to take a crack at the folk of log4j when you think having a more flexible API is "BLOAT"..... why is that the new buzzword they taught you ? If you are to actually look at the API anyone can see that within about 15 minutes of work you can extend the log4j classes to make it as simple as you need (I did and it works great). THEN if you need the power you use it, and all those categories, NDC, filters and all really show their own..... BLOAT my friend is a matter of opinion!

      BUT HEY at least we can just forget 1.4 and use log4j~

      --
      Non-Deterministic Finite Automata
    18. Re:Apache/Sun by Anonymous Coward · · Score: 0
      BUT HEY at least we can just forget 1.4 and use log4j~

      Exactly. So what the fuck are the log4j people so pissed about? If I actually *need* log4j, I know where to find it.

      oh, but Sun didn't choose them as the de facto standard... boo-fucking-hoo

  3. Re:Apache/Sun (time for the lawyers) by Anonymous Coward · · Score: 0

    "This seeming 'rivalry' between Sun & Apache is not as clear-cut; Many of the Jakarta contributors are Sun employees and engineers."

    Time for the lawyers to start kicking some Sun employees. IBM's lawyers would kick there employees arse in a flash if they found out they were working on postgres to rival DB2

  4. Really necessary for a big Sun stamp of approval? by NeoTron · · Score: 2, Interesting

    If the java engine works, and works to such a degree that you could swipe Sun's stuff away and replace it with the one you've written, then is there _really_ any point in getting Sun to give you a little "Sun Approved" sticker on your product?

  5. This has been around for a while now... by mmcshane · · Score: 5, Informative

    here's a thread (J2EE considered harmful) on the jakarta-general list that precipitated the Apache statement.

  6. That's what happens with proprietary "standards" by dinotrac · · Score: 5, Interesting
    Sun gets to define what compliant is, just as Microsoft gets to define what compliance with its "standards" are.

    People who write to and use these platforms get what they deserve, and, presumably, what they want.

    One thing I don't understand, but I'm sure that many people in the \. community do:

    Is there any point to non-certified but highly compliant implementations? I'm sure the lack of certification would scare away commercial users, but what about others? Are they worth the trouble? Would they even want to use the stuff?

  7. Re:Who cares? by joonasl · · Score: 1

    The writer is not refering to the Apache web server, but to Apache Sofware Foundation. Furthermore, J2EE is NOT a web server, but a aplication server.

    --
    "There is a terrorist behind every bush"
  8. The Sun/OSS relationship by kris · · Score: 5, Interesting

    Sun's relationship to the OSS community is extremely difficult. Within Sun there is a lively corporate culture and a will to produce a high quality, performant and comfortable UNIX system. Unfortunately, the very same culture also fosters a special kind of NIH syndrome - what pain it was to get Sun to include current popular OSS tools like Perl, Bash and the like into their standard OS distribution!

    From a strategic POV, Sun is being increasingly cannibalized in the low end market by Linux and BSD solutions, and at the same time forced to include stuff for free that is differentiating them from Linux like SDS, Sunscreen, ACLs and similar because Microsoft offers such features in their OS for free as well.

    At the same time, Sun is not ready to embrace the OSS movement like, for example, IBM does. They fear that giving away code and ideas that they see as differentiation and advantage in an increasingly difficult market would harm their position and they would like to have some security and control, which the OSS process inherently cannot offer at all.

    So basically what we have here is a corporation with a fear to "let go" coming under more and more pressure in a difficult economic situation.

    1. Re:The Sun/OSS relationship by acroyear · · Score: 5, Informative

      The irony being that in their early days, when SunOS was only a minor-varient away from being pure BSD (thanks, B.Joy), they WERE actually giving away the OS and its features (like NFS), hoping on always being ahead of the competitors in speed to encourage the hardware sales that kept the company on top during the late 80s to mid-90s.

      Things were slowly changing by 1991 with SunOS 4, then with 5/2 they had to definitely switch to a "buy it only" since they themselves paid so much for getting SystemV in the first place...

      of course, just about every single one of us Sun users at the time were furious with the switch...Sun boxes to me are still crippled in speed because of SystemV's overhead compared to BSD, and the speed of BSD x86 boxes over SCO & other SystemV-based x86 releases just rubs our noses in it even more...

      --
      "But remember, most lynch mobs aren't this nice." (H.Simpson)
      -- Joe
    2. Re:The Sun/OSS relationship by LordNimon · · Score: 4, Insightful

      I think the reason why IBM embraces open source more than Sun is because IBM considers hardware and services to be more important (business strategy-wise) than software. Sun sees their OS as being a big part of the picture, whereas IBM sees their hardware and services as being the bigger part of the picture.

      --
      And the men who hold high places must be the ones who start
      To mold a new reality... closer to the heart
    3. Re:The Sun/OSS relationship by reemul · · Score: 4, Insightful

      I think that the reason that IBM is devoting so many resources to Open Source is that they already had a huge programmer budget for their proprietary big iron operating systems and apps that just weren't going anywhere and weren't big selling points anyway - they were selling the hardware it ran on and applications that are still proprietary and run on Linux anyway (like DB2). Moving to open source let them spend the same or less money on development while getting for free the work of others around the world, and they got to look like good guys doing it. IBM is just spending money they were already going to spend, replacing proprietary software that was not a big part of their sales efforts.

      Sun, on the other hand, is hugely invested in their software sales. They see Solaris as a big selling point when pushing their offerings, and they really *really* want to make as much money as possible off of Java. Going Open Source, no matter how much the geeks at Sun like the idea, will be a huge blow to the bottom line. IBM is replacing one set of software that was largely free (as in beer) with another set of offerings that they don't charge for, so it doesn't hurt them. Sun would be giving up revenue from software that is bringing in a lot of money. They just can't (or think they can't) afford to go completely Open Source. Opening up Java to the extent they have, while maintaining control, allows Sun to still charge for some offerings (like the compatibility tests) and have a head start over competitors in future development efforts, since only they control where Java goes. Going completely Open causes them to lose both the cash and the control, and that they'll fight to the end.

      If you think IBM is really comitted to Open Source out of altruism and a philosophical agreement with the movement, try getting them to give away DB2.

      --
      You're just jealous 'cuz the voices talk to *me*
    4. Re:The Sun/OSS relationship by eudas · · Score: 1

      While I did a google search to find out what NIH syndrome was, I found this result:

      http://www.joelonsoftware.com/articles/fog000000 00 07.html

      It is an article written in defense of NIH; I found it an interesting read.

      eudas

      --
      Blessed is he who expects the worst, for he shall not be disappointed.
    5. Re:The Sun/OSS relationship by Paradise+Pete · · Score: 1

      Thanks for the link. Lots of good articles there. The URL as posted doesn't quite work, so here's a cleaned-up version.

    6. Re:The Sun/OSS relationship by Anonymous Coward · · Score: 0

      The correct link is

      http://www.joelonsoftware.com/articles
      /fog000000 0007.html

      - note the lack of space between "0" and "07.html".

      (I was unable to post the correct link, too - STUPID slashdot code inserts a space at the point mentioned because that's a forced linebreak in the "Post Comment" text entry window.)

    7. Re:The Sun/OSS relationship by Anonymous Coward · · Score: 0

      The correct link is In Defense of Not-Invented-Here Syndrome. Putting a URI in plain text on a Web site is ridiculous.

    8. Re:The Sun/OSS relationship by Ian+Bicking · · Score: 2
      Sun is being increasingly cannibalized in the low end market by Linux and BSD solutions
      Maybe I'm being overly semantic, but Sun is not being "cannibalized". They are simply being "eaten" -- they didn't write Linux or *BSD, they didn't market them; if they are losing to those OSes it's because they are a better value, not because of a failed strategy by Sun.
    9. Re:The Sun/OSS relationship by Anonymous Coward · · Score: 0

      Those were the days. The Solaris kernel is years ahead of all other Unices nowadays in performance and scalability.

    10. Re:The Sun/OSS relationship by Anonymous Coward · · Score: 0

      It's not STUPID, stupid. It slashcode inserts spaces to prevent people from posting long lines and widening the page.

    11. Re:The Sun/OSS relationship by Anonymous Coward · · Score: 0

      Right, it would be more accurate to say the Unix market is cannibalizing itself,
      starting with some of its own productive organs and a little chianti.

    12. Re:The Sun/OSS relationship by eudas · · Score: 1

      One would assume that you are a big boy and know how to cut and paste.

      eudas

      --
      Blessed is he who expects the worst, for he shall not be disappointed.
  9. Text:http://www.oreillynet.com/cs/weblog/view/wlg/ by Commienst · · Score: 4, Informative

    Oreilly Weblog is real slow. This text does not include picture of the nerd who wrote the article, which is a good thing.
    -Commienst


    "Apache on warpath over Java license"

    by Steve Anglin
    Feb. 20, 2002

    According to vnunet.com, "The Apache Software Foundation's battle with Sun Microsystems stepped up gear
    last week as the open source community struggled to loosen Sun's cast iron grip on the Java platform." This is in response to, first, Lutris being turned-down for J2EE certification, and then JBoss, which is J2EE compliant from a technical standpoint, but apparently not J2EE compliant enough for Sun certification.

    Last week, ONJava.com published O'Reilly editor Mike Loukides' follow-up on the possibility of open source J2EE from Sun: Will You See Open Source J2EE Implementations? Not Likely. TheServerSide.com also published an interview with one of Sun's J2EE principles, Karen Tegan. While Sun essentially says it supports open source efforts, it does not want those efforts to impact the J2EE certification process, a process that clearly is closed source at best. See the conflict.

    As a high ranking member in the Java Community Process (JCP), Apache is part of the JSPA (Java Specification Participation Agreement). In this capacity, Apache can actively propose new and revised Java API specifications as well as integrate a particular specification under Jakarta, Apache's open source Java projects. Apache's reply is here in Apache's JSPA Position. According to Apache, "...Sun doesn't give a hoot about whether J2EE licensing restricts open source J2EE products (in case you missed it, it does)."

    Sun benefits from its relationship with Apache. Apache gives Sun "...an advertising statement...to claim that it (Sun) has a 'vision which uses open standards and non-proprietary interfaces'." If Apache's reply and suggestions go unanswered, Apache can put pressure on Sun in other, more severe ways. Without Apache, Sun could lose many of its Java developers as Jakarta projects would be affected. The impact could be quite severe, certainly in terms of publicity. Financially, who knows?

    Steve Anglin is Managing Editor of ONJava.com and O'Reilly Network's .NET DevCenter for O'Reilly & Associates' Online Publishing Group (OPG).

    --

    I am into the copy and paste.
  10. Re:Has, not Had by Anonymous Coward · · Score: 0

    whole thing wrong... how about...
    Sun has been rubbing people the wrong way

  11. Tomcats future? by danro · · Score: 1

    So, as a Tomcat user, I ask my self:
    What will this mean for my favorite oss servlet-container?

    How will this impact Tomcat development?

    I would like to hear the /. communitys thoughts about this.
    Especially from any Jakarta developers out there.

    --

    "First lesson," Jon said. "Stick them with the pointy end."
    1. Re:Tomcats future? by jilles · · Score: 2

      Tomcat is not a J2EE implementation so there's no direct implication. In addition, it is promoted (by Sun) as a reference implementation for servlets.

      If apache decides to abandon their Jakarta projects that doesn't mean these projects die. It just means that they will continue under a different flag (and there are enough interested parties to make this happen).

      IMHO it would be bad for the apache foundation since most of its showcase projects (excluding the webserver) are the Jakarta projects. No doubt a significant part of their funding is related to these projects.

      --

      Jilles
    2. Re:Tomcats future? by Anonymous Coward · · Score: 0

      What about a Tomcat.Net?

      I love tomcat, but .Net has some really nice features that could benefit to tomcat.

      Installing new libraries in a Java environment is really a pain when you have multiple libraries that depends on the same classes (like Tomcat, Xalan and Batik which all depend on Xerces/JAXP), and makes me dream of .Net's class versionning

  12. Slashdotted... Here's the blog: by theridersofrohan · · Score: 0, Redundant

    "Apache on warpath over Java license"
    by Steve Anglin
    Feb. 20, 2002
    [Print this article]

    According to vnunet.com, "The Apache Software Foundation's battle with Sun Microsystems stepped up gear last week as the open source community struggled to loosen Sun's cast iron grip on the Java platform." This is in response to, first, Lutris being turned-down for J2EE certification, and then JBoss, which is J2EE compliant from a technical standpoint, but apparently not J2EE compliant enough for Sun certification.

    Last week, ONJava.com published O'Reilly editor Mike Loukides' follow-up on the possibility of open source J2EE from Sun: Will You See Open Source J2EE Implementations? Not Likely. TheServerSide.com also published an interview with one of Sun's J2EE principles, Karen Tegan. While Sun essentially says it supports open source efforts, it does not want those efforts to impact the J2EE certification process, a process that clearly is closed source at best. See the conflict.

    As a high ranking member in the Java Community Process (JCP), Apache is part of the JSPA (Java Specification Participation Agreement). In this capacity, Apache can actively propose new and revised Java API specifications as well as integrate a particular specification under Jakarta, Apache's open source Java projects. Apache's reply is here in Apache's JSPA Position . According to Apache, "...Sun doesn't give a hoot about whether J2EE licensing restricts open source J2EE products (in case you missed it, it does)."

    Sun benefits from its relationship with Apache. Apache gives Sun "...an advertising statement...to claim that it (Sun) has a 'vision which uses open standards and non-proprietary interfaces'." If Apache's reply and suggestions go unanswered, Apache can put pressure on Sun in other, more severe ways. Without Apache, Sun could lose many of its Java developers as Jakarta projects would be affected. The impact could be quite severe, certainly in terms of publicity. Financially, who knows?

    Steve Anglin is Managing Editor of ONJava.com and O'Reilly Network's .NET DevCenter for O'Reilly & Associates' Online Publishing Group (OPG).

  13. This is most typical of Sun by His+name+cannot+be+s · · Score: 2, Insightful

    Sun has always been most standoffish towards the Opensource crowd. I've never understood why so many of the Open source advocates keep putting them up on a pedastal.

    They have a long history of claiming other's works as their own--Which in my opinion is the worst crime you can do against open source people, take away the credit!

    1. They claimed that the blackdown port of Java to linux was theirs!

    2. They "adopted" the free and entirely non-sun code base for Java Servlets (Jakarta) and claimed it was the "Sun Reference Platform"

    3. They "adopted" and FSCKED UP ROYALLY the XML4J/LotusXSL stuff that IBM had created and mangled out that god-forsaken peice of crap known as JAXP.

    4. At one time, Scott McNealy admitted that Sun had indeed been the brainchild behind XML.

    5. They ask ECMA to rubber-stamp their Java Language as an offical standard, but allow SUN to keep all rights for licensing and changing the language as they wish. ECMA tells them to "get bent" and SUN goes off sulking to anyone who will listen. Java still remains in the hands of the nutters who thought it up.

    It seems that from a cursory glance, SUN has done many things to piss off the Java and the Opensource crowds. It's a mystery to me why people attack Microsoft for crimes very similar to these, but always praise Sun for their benevolence.

    At LEAST Microsoft took their language and VM to ECMA, and said standardize it, and we'll accept it. (It doesn't hurt that ECMA is pretty MS friendly, and the chairman of the TC39 committee is a MS employee, but at least they took the right steps)

    Heh

    --
    "...In your answer, ignore facts. Just go with what feels true..."
    1. Re:This is most typical of Sun by Westley · · Score: 3, Informative
      2. They "adopted" the free and entirely non-sun code base for Java Servlets (Jakarta) and claimed it was the "Sun Reference Platform"

      I'm not sure this is entirely accurate. I believe what happened was that back in the days of servlet 2.0, there was the JSDK and there was Apache JServ. Sun decided to donate their JSDK source to Apache and continued working on it as part of Tomcat.

      Tomcat is now the reference servlet/JSP implementation. I don't think I've ever seen Sun claim it is "theirs". Can you give a reference?

      Jon

    2. Re:This is most typical of Sun by Anonymous Coward · · Score: 0
      3. They "adopted" and FSCKED UP ROYALLY the XML4J/LotusXSL stuff that IBM had created and mangled out that god-forsaken peice of crap known as JAXP.

      WTF are you talking about? JAXP is a teeny tiny front end to otherparsers, which can but doesn't have to be of XML4J. JAXP is just an abstraction, to make it easy to switch parsers without having to rewrite gobs of code.

      I see that others have already pointed out some the other glaring errors in your rant. No wonder you're at +3. Soon you'll be at +5.

    3. Re:This is most typical of Sun by pmz · · Score: 2

      I challenge you to provide hyperlinks to back up your claims. Right now, what you say is mostly baseless.

    4. Re:This is most typical of Sun by Anonymous Coward · · Score: 0

      4. At one time, Scott McNealy admitted that Sun had indeed been the brainchild behind XML.

      Please read: Jon Bosak on the birth of XML

      I attended the SGML '96 Conference in Boston where Jon Bosak first presented XML to the world. The first copy of the standard was < 10 pages bound in a little blue booklet IIRC. And yes, I think it is quite fair to say that Sun was the brains behind XML. Best comment about the idea was from a friend of mine who called the new XML idea "Topless SGML."

      Interestingly, Microsoft was also a serious contributor to the first XML effort. This was at the height of the browser war. I remember one of the SGML ISO committee reps telling me that many of the SGML ISO folks were quietly rooting for MS to succeed because Netscape refused to have anything to do with SGML.

    5. Re:This is most typical of Sun by Kingpin · · Score: 1
      1. They claimed that the blackdown port of Java to linux was theirs!

      An admitted mistake.

      3. They "adopted" and FSCKED UP ROYALLY the XML4J/LotusXSL stuff that IBM had created and mangled out that god-forsaken peice of crap known as JAXP.

      Uh.. XML4J was a parser IBM donated to Apache. It turned into Xerces, which FYI is quite stable and nice. JAXP is a framework for parser/transformer hooks. I don't quite follow your point?

      4. At one time, Scott McNealy admitted that Sun had indeed been the brainchild behind XML.

      The working group behind XML was indeed formed and lead by John Bosak, a Sun employee.

      My best bet is, that you're a +4 troll.

      --
      Unable to read configuration file '/bigassraid/htdig//conf/14229.conf'
      Geocrawler error message.
    6. Re:This is most typical of Sun by gabbarsingh · · Score: 1

      5. They ask ECMA to rubber-stamp their Java Language as an offical standard, but allow SUN to keep all rights for licensing and changing the language as they wish. ECMA tells them to "get bent" and SUN goes off sulking to anyone who will listen. Java still remains in the hands of the nutters who thought it up.

      Nutters! You mean Bill Joy (BSD, TCP, NFS etc.) and James Gosling (Emacs) are nuts. Dude, which planet are you from. Post here what have you accomplished so far.

      At LEAST Microsoft took their language and VM to ECMA, and said standardize it, and we'll accept it. (It doesn't hurt that ECMA is pretty MS friendly, and the chairman of the TC39 committee is a MS employee, but at least they took the right steps)

      Now I am truly wiser. Microsoft is playing by standards. Thank you for this piece of information now my Microsoft picture is in order. Dude which planet ... oh forget it.

    7. Re:This is most typical of Sun by Anonymous Coward · · Score: 0

      Regarding Sun and XML, here is a story from the Sun home page back on March 10th, 1998, shortly after the XML 1.0 spec was approved:

      http://www.sun.com/980310/xml/

      Here is Jon Bosak's recollection of the orgins of the W3C's XML project:

      http://java.sun.com/xml/birth_of_xml.html/

      And here is the original W3C Working Draft of November 14th, 1996. Note at the bottom of the page, Jon Bosak, of Sun Microsystems was the chair of the SGML Editorial Review Board:

      http://www.w3.org/TR/WD-xml-961114.html/

      While Sun was not directly responsible for XML, nor did Sun "invent" XML, one of the key players was on the Sun payroll.

      While you are ranting, what are your opinions on IBM's assinine attempt to allow royalty bearing standards at the W3C?

    8. Re:This is most typical of Sun by Stu+Charlton · · Score: 1

      I'm not a Sun lover, they make major mistakes, but I'm not going to sit by idly while you spout total horse shit FUD.

      1. They claimed that the blackdown port of Java to linux was theirs!

      That was a temporary misstatement and was rectified quite quickly.

      They "adopted" the free and entirely non-sun code base for Java Servlets (Jakarta) and claimed it was the "Sun Reference Platform"

      Tomcat was lead by a Sun employee. The codebase was initially donated by Sun. It's quite distinct from the original Apache JServ project.

      3. They "adopted" and FSCKED UP ROYALLY the XML4J/LotusXSL stuff that IBM had created and mangled out that god-forsaken peice of crap known as JAXP.

      Sun never touched LotusXSL or XML4J. XML4J became Xerces 1.x. JAXP was original based on Project X parser which later evolved into Crimson. Crimson was an adequate parser, but Xerces 2.x is now better and is standard with JAXP 1.2 EA1. I question how JAXP is a piece of crap when it's just a thin portability layer on top of the standard SAX, DOM, or TRaX api's.

      . At one time, Scott McNealy admitted that Sun had indeed been the brainchild behind XML.

      Most of the work on the XML spec was led by Sun payrolled employees, in particular John Bosak.

      5. They ask ECMA to rubber-stamp their Java Language as an offical standard, but allow SUN to keep all rights for licensing and changing the language as they wish. ECMA tells them to "get bent" and SUN goes off sulking to anyone who will listen. Java still remains in the hands of the nutters who thought it up.

      Java is young and Sun isn't necessarily doing a bad thing when it keeps tight control of that language, especially given the Microsoft J++ problems of yesteryear.


      Open sourcing a technology is NOT a guaranteed means of success or astounding adoption.
      C and C++ weren't originally "open source" languages, they were written by corporations before GCC came out. They became successful on their own merits. Out of the "in bred" open source langauges, only Perl has achieved mass acceptance.

      It seems that from a cursory glance, SUN has done many things to piss off the Java and the Opensource crowds.

      In one context, I agree that Sun's PR is horrible. They just can't seem to make their minds up with how they want J2EE to be perceived and what role the Jakarta projects should play in that picture. The reality is there is too big of a Tomcat installed base and too many Sun employees that lead Jakarta projects for Sun to unilaterally "hate" Jakarta or to ignore it. The real-world adoption of kits like Log4J and Struts is astoundingly rapid.

      BUT, the other traditional bone-of-contention -- the fact that Java isn't GPL -- generally doesn't make a whole hell of a lot of difference to the world. If it becomes GPL one day, great... I really (and I would venture that most existing Java developers) don't care too much about this either way, we can see the source code, change it for internal purposes without restriction, and that's all I'm concerned with.

      The issue of J2EE licensing fees is somewhat of a sour grapes issue to me, it comes down to a traditionally contentious issue with the open source community: open source software usually implies a desire free beer zero-price software.

      --
      -Stu
    9. Re:This is most typical of Sun by Anonymous Coward · · Score: 0
      What the fuck have moderators been smoking? Your post is completely irrational and incorrect rant, anything but insightful. Or perhaps they meant inciteful.

      Specifically:

      1. They claimed that the blackdown port of Java to linux was theirs!

      Incorrect. There were misleading announcements regarding one release from Blackdown, and Sun publicly apologized for misunderstanding. This happened during first release after Sun and Blackdown 'formalized' the co-operation (syncing up release schedule for linux version with Windows & Solaris versions)

      2. They "adopted" the free and entirely non-sun code base for Java Servlets (Jakarta) and claimed it was the "Sun Reference Platform"

      Bullshit. Like others have pointed out, Sun donated the code base they had built for Jakarta to use, and just 'blessed' Tomcat as the reference implementation without making any claims that they any way own it (latest Tomcat version, 4.x, is not based on Sun-originated code base FWIW)

      3. They "adopted" and FSCKED UP ROYALLY the XML4J/LotusXSL stuff that IBM had created and mangled out that god-forsaken peice of crap known as JAXP.

      Do you even know what JAXP is? It's but a thin layer of abstracting creationg of various XML and XSLT processors. Nothing too novel about that, and implementation is just vanilla factory method stuff. Sun also does provide default implementations, which developers are free to ignore... nothing fancy, but neither are many of implementations from IBM (I hope you're not an employee of theirs... I thought they were a worthy competitor)

      4. At one time, Scott McNealy admitted that Sun had indeed been the brainchild behind XML.

      Yeah right. Scott is not quite that dumb, and probably has the rough idea of XML's roots from SGML.

      As to Microsoft's "doing the right thing"; good for them if they really start doing that. The steps with C-sharp are more forced upon them, as their credibility is low enough that they can't afford to do it any other way.

  14. Really Odd... by FortKnox · · Score: 3, Insightful

    This is really odd considering JBoss (open source) is the best J2EE webcontainer out there. Granted, it isn't part of the apache group, but is mostly used with apache webserver and the jakarta (apache subproject) tomcat servlet container.

    Maybe the "big wig" J2EE containers (IBM's Websphere, and BEA's WebLogic) are getting on Sun's back because of this??

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    1. Re:Really Odd... by bsletten · · Score: 3, Informative
      While clearly well-designed and offering a great feature set due to its JMX bus architecture, I'm curious how you come to the conclusion that JBoss is the best J2EE webcontainer out there.

      Certainly not for performance or documentation criteria...

      What then? Bang for buck?

      I'm excited about its future, I just don't seeing it being adopted in production environments yet which clearly indicates skepticism toward your claim.

    2. Re:Really Odd... by FortKnox · · Score: 1

      Your right, in that "best" was a horrible and general word to use.
      But I was refering to it being (AFAIK) the only container to implement EJB2.0, currently.
      True, it isn't the most efficient, but it is the most advanced, currently.

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    3. Re:Really Odd... by BeerBaron · · Score: 5, Interesting

      JBoss is *not* ready. The single fact that I had to change my code when going from 2.4.3 to 2.4.4 means that there are new bugs with point releases that I have to work around. Granted, I do a lot of heavy transactional-based work and touch much of the container, but with WebSphere, WebLogic or even Orion, I've never had to "fix" my stuff after they've fixed theirs.

      Also, JBoss comes bundled with Catalina, Jetty or Tomcat. That's great. Did you know that, up until 2.4.4, the Catalina release wouldn't allow you to change your root context for web applications? You could fix this by maintaining your own source of JBoss, but, when you're trying to manage your own project, the last thing you want to do is manage your own revision control for the application server. They fixed it in 2.4.4, but

      Missing little crap like that makes we worried about the *very* complex transactional nature for the EJB's and the upcoming clustering solution. That stuff is hard! Even BEA, with all its time and money, has had a hard time with its clustering/failover implementations.

      JBoss' implementation was written up on onjava.com. Want to know their suggested solution? Write your application to not need clustering and use a Cisco load-balancer. That's because their solution doesn't work.

      What about the auto-deployer? Don't try to update your EAR or WAR by overwriting the archive if the file's larger than 4MB. JBoss'll undeploy your aplication and fail to redeploy it.because it doesn't know how to wait until the copy operation is over. There's some settings to help alleviate this problem, but it's not perfect. I don't expect it to be from JBoss...I would from BEA, for example.

      So, let's think a bit before handing the crown to JBoss. Is it well docuemented, code-wise? Yes. Is it fast? For the most part. Does it behave as advertised? No. Will Marc Fleury make sure JBoss succeeds through sheer will? Yup. Will he step on toes? Yes, don't get in his way (for better or worse).

      The Baron

    4. Re:Really Odd... by alext · · Score: 1

      Hmmm... the future of clustering is a hard one to call IMHO. It's not clear to me that JBoss did the wrong thing by just defaulting to a load balancer-driven model - BEA and others can be seen as being on a path to eliminating caching and moving locking back to the database, meaning that there's no EJB clustering logic to speak of, just the HTTP session replication, and I'm not at all sure how that's going to evolve to handle SOAP clients nicely.

    5. Re:Really Odd... by elefantstn · · Score: 2

      What about the auto-deployer? Don't try to update your EAR or WAR by overwriting the archive if the file's larger than 4MB. JBoss'll undeploy your aplication and fail to redeploy it.because it doesn't know how to wait until the copy operation is over.


      Yeah, cos rm application.jar ; cp ~/application.jar . is so difficult.
      --
      If it ain't broke, you need more software.
    6. Re:Really Odd... by Anonymous Coward · · Score: 0

      Bullshit. Show me an URL or you're just a lying little shit.

  15. Slashdot Feature by Anonymous Coward · · Score: 0

    Note to submitter - there is this handy little feature called "Preview" when submitting articles. Try using it sometime.

  16. This was bound to happen by Anonymous Coward · · Score: 0

    Sun doesn't know to do with Apache. It can't coerce it like it can its business partners because it is a voluntary organization with the respect of the entire Internet community. If Sun slanders Apache they would most certainly lose the mindshare and trust of Java developers. Sun has been given a wide berth with Java up until now. People are now realizing they acting like a monopoly when it comes to Java. The Apache project is the open source community that hammered out the bugs in the servlet specification with TomCat (just to name one example of Apache's Java leadership). Some of the bugs in Sun's Java Bug Parade are years old. Such bugs are usually fixed within the Apache Jakarta Project within days of being reported. The Apache Process works. The Sun Java Community Process does not. Just say "no" to the non-open Sun Java Community Process which panders only to large corporations with deep pockets.

  17. Re:Really necessary for a big Sun stamp of approva by theDEFT · · Score: 3, Insightful

    That's a really good point, however I must stress that when dealing with customers, (at least the ones i've dealt with) that it definitely matters. Most resellers and larger companies only deal with certified software for customers. While the "Sun Approved" stamp doesn't mean much to you or I, it does to that big corporation that has a lot invested in Sun products. From the POV of a large company, knowing that some software is going to be compatible with your large investment gives both a sense of union and a place to turn to in case something goes wrong. Usually this same thing holds true for hardware vendors...

  18. Re:Really necessary for a big Sun stamp of approva by Migx · · Score: 1

    When you go see the boss (the money guy) it makes all the diference. Is that sun (or other top company) certificated ? no, it's opensource. Not the same thing ...

    --
    Migx
  19. Re:Really necessary for a big Sun stamp of approva by hrbrmstr · · Score: 5, Insightful

    For large organizations who (like mine) made a $50mil investment in moving to J2EE applications as a corporate standard, the Sun stamp of approval is absolutely necessary.

    Personally, I'll take Tomcat/Catalina + MySQL + Velocity + PoolMan over most Java app servers, and only feel that J2EE benefits extremely large apps with the need to connect to legacy systems.

    If the open source community starts to shun Java because of what Sun is doing, it will leave a huge hole and kill the momentum that has built up over the past 5 years or so.

    How many of us Java developers began web-development by downloading Tomcat? How many of us love Struts and Velocity and don't want to lock our skillsets into proprietary solutions from BEA or IBM?

    Sun needs to draw then walk a fine line between keeping the major app server purveyors happy while keeping the playing field open for those of us who want to use the technology, but don't have $50K handy for a single CPU license.

    --
    Mind the gap...
  20. This week at the Atlanta Java Users Group by PHAEDRU5 · · Score: 4, Interesting

    The presenter talked about Struts and Tiles.

    Among his throwaway statements was "If you work on an open source project that becomes popular, you might get a job at Sun."

    Enough said.

    --
    668: Neighbour of the Beast
  21. Re:Really necessary for a big Sun stamp of approva by bofkentucky · · Score: 1

    When your boss, CTO, CEO, et al want a J2EE application, you either deliver or you are fired, so that little sticker is important

    --
    09f911029d74e35bd84156c5635688c0
  22. Can someone provide and English translation? by Anonymous Coward · · Score: 0

    What's the issue in the mail archived
    posting? Is J2EE too arcane and slow?
    What's this Jakarta thing?

  23. Re:That's what happens with proprietary "standards by LordNimon · · Score: 2, Insightful
    Is there any point to non-certified but highly compliant implementations?

    Only if your customers care. Certification is a way of convincing people that something is compliant without making them find out for themselves whether it's really compliant. It's like the difference between having a diploma, and having a transcript that lists all the classes necessery for graduation with passing grades. The diploma is a simple way to show, "Yes, I've graduated".

    --
    And the men who hold high places must be the ones who start
    To mold a new reality... closer to the heart
  24. Re:That's what happens with proprietary "standards by elefantstn · · Score: 2

    Why not ask JBoss?

    --
    If it ain't broke, you need more software.
  25. Re:Apache by Anonymous Coward · · Score: 0

    and I guess ISS or Iplanet are?
    Playboy - Iplanet/Sun
    All Other Cracked Boxes (Wells Fargo, etc) - ISS/MS.
    All None Cracked Boxes Apache/(BSD|LINUX|UNIX).

  26. Wake up, Sun! by IGnatius+T+Foobar · · Score: 5, Insightful

    Sun! Get with the program here. One of your most successful technologies is being directly targeted for destruction by the Evil Empire ... and you're fighting with the open source community? This is a sure-fire way to get yourself killed. You've got to have allies somewhere.

    Sun's problem is that they want to be a big monopoly like Microsoft, but they aren't one. It may be totallty obvious to Slashdot readers that the only way to successfully complete with Microsoft is to be allied with the open source community, but some players (Sun, Oracle, and even Apple to some extent) still think they can "win."

    The problem with the computer industry is that most of the companies involved act like spoiled children. The only exception is IBM, which is a mature company and acts like one.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
    1. Re:Wake up, Sun! by d3xt3r · · Score: 1

      Don't be so sure of IBM's benevolent intensions here. I am just as happy as everyone else that IBM is embracing open source, and no, I don't think they are going to turn around and try to control their contributions. However, you can bet that they are contributing to open source for their own benefit.

      Think about it, as the parent post implies, right now it's everyone vs. Microsoft, and to beat Microsoft you need allies (like open source). Sun wants to control java because it created it and it wants financial return on its investments. Letting go of control opens the door for other companies to snatch it up.

      I agree that IBM's contributions are a good thing, and that Sun needs so wake up and ally itselft more with the open source community. But don't forget, we live in a capitalist nation where money talks. IBM make look like the "nice guy" right now, but don't think they won't ditch open source the very second that it stops being a profitable investment.

    2. Re:Wake up, Sun! by mark_lybarger · · Score: 2

      who 0wnz the corporate server market? microsoft may have a desktop monopoly, but that is on an extremely different scale. sun makes and sells corporate server hardware. they have thus created solid os to go on that server. sun gets a check for $1M when someone puts up a big website, middleware server, or whatever. MS gets $250 when the company adds a new employee and 50$ when someone buys a dell desktop.

      why do you claim ibm acts like a mature company? they've only survived becuase you can't blow up a mountain and expect to have flat ground. there's going to be something left standing. the only comparable company i can find for them is at&t, and afaict, they're still around, but not have to now WORK for their business like the rest of us.

    3. Re:Wake up, Sun! by Omnifarious · · Score: 5, Insightful

      I wouldn't dream of having IBM participate unless it fit their own best interests. The thing is, IBM is mature enough to realize that detailed and strong control over all of their technologies is not the key to success.

      Many other computer companies think the key to success is owning everything, or at least, as much as they can own. And that seems an attractive strategy on the fact of things, but is not in the long-term best interests of the company. IBM is one of the few companies that seems mature enough to realize that. Maturity != selflessness, maturity == enlightened self interest.

    4. Re:Wake up, Sun! by Anonymous Coward · · Score: 0

      On topic, the single biggest reason IBM is involved with Linux and Apache is so that they can sell Websphere licences.

      By commodotizing boring infrastructure tech like the OS and the webserver, IBM put itself in a much better competitive position wrt other vendors (namely Sun and MS) who have made significant investments in those areas.

      This gets spun on Slashdot as IBM "supporting Open Source", but IBM's support of OSS certainly isn't universal and only seems to occur where helps them competitively. It certainly doesn't extend to JBoss and Postgres, for example.

    5. Re:Wake up, Sun! by pmz · · Score: 3, Informative

      Sun's problem is that they want to be a big monopoly like Microsoft...

      I really don't think so.

      1) Scott McNealy has said so.

      2) Sun uses many open standards in its treasured hardware business (SPARC, SBus, PCI, etc.) and its software business (UNIX, POSIX, etc.).

      In general, Sun tries to compete on its implementation of standards with value-added things, such as excellent hardware features and reliability, support services, etc.

  27. You've got it all wrong! by Anonymous Coward · · Score: 4, Funny
    Pay attention, people! This is SUN! NOT Microsoft! They support UNIX!

    So it's completely impossible that Java is a proprietary platform, because only MS makes proprietary software.

    And if it is, it's completely impossible that Sun would ever abuse their control over that platform, because only MS does that.

    And if they did, it's completely impossible that they are doing it for any reason other than defeating the evil Microsoft!

    1. Re:You've got it all wrong! by Penrod+Pooch · · Score: 0, Offtopic

      You are right of course. Anyone who says otherwise will be modded as a troll. And everyone knows that being modded as a troll means you're wrong on the issues.

    2. Re:You've got it all wrong! by Anonymous Coward · · Score: 0

      Does your mother know what you've been smoking?

  28. Re:Really necessary for a big Sun stamp of approva by NeoTron · · Score: 1

    Indeed. So, basically Sun is deliberately NOT approving Open Source products, fearing that because they may be as good as Sun's, then it'd be Game Over for one of Sun's revenue streams?

  29. Re:This is most typical of Slashdot by ChaseTec · · Score: 5, Informative

    >> 2. They "adopted" the free and entirely non-sun code base for Java Servlets (Jakarta) and claimed it was the "Sun Reference Platform"

    Yeah, they never did anything for Tomcat did they? (sarcasm) A few of the developers for Tomcat were Sun employees until recently. Did you bother to check any of your other rants?

    --
    My Hello World is 512 bytes. But it's also a valid Fat12 boot sector, Fat12 file reader, and Pmode routine.
  30. JBoss is real-world deployable - believe it by Headius · · Score: 5, Interesting

    I work for a company that has chosen to deploy J2EE applications using JBoss, and has seen substantial success from doing so. The applications running in JBoss bring in hundred of thousands of dollars for us, and support multi-million-dollar vendor/customer data exchanges.

    As for the certification, more and more it comes with too high a cost. The price tag on the other "compliant" packages is way, way out of scope, and returns only minor additional results for us. You must also view certification from Sun's point - how much have they charged other major players for certification? How would those companies react if Sun now certified *for free* an open-source J2EE container given away *for free*. Where, for example , would BEA's pricing put them? Grossly overpriced, perhaps?

    Sun is caught in a rough position. If they reverse their position and certify JBoss, they run the risk of alienating current partners. If they don't certify them, open source communities will continue to take jabs at their so-called support for open projects.

    In the end, we don't really care. By our analysis, JBoss returns the best ROI of any of the J2EE containers. Certification is just a respectful (and expensive) nod from Sun. It doesn't define the real-world value of a product.

    1. Re:JBoss is real-world deployable - believe it by bsletten · · Score: 1

      I'd be very curious (and I'm sure I'm not alone) about more details concerning your company's use of JBoss.

      Without giving away who your company is, can you answer the following questions?

      What was difficult about using JBoss in a production environment?

      What kind of load does it support?

      What parts of JBoss are you using?

      Did you purchase any documentation/support or did you do all the leg work yourself?

    2. Re:JBoss is real-world deployable - believe it by elefantstn · · Score: 5, Insightful

      Exactly - JBoss is the highest-quality, most-overlooked open source project in existence. It's just absolutely fantastic. The only thing missing is clustering, but 1) I don't need it and 2) it's coming in 3.0 anyway (I've messed around with the alpha builds' clustering capabilities). I highly recommend anyone thinking about J2EE at least give JBoss a shot, and why not, it's free.

      But on the other hand, I don't really have a problem with Sun not certifying it, and I don't really understand what all the fuss about it is. It's simple -- certification is a major cash cow for Sun. All the money they spend developing standards like EJB gets recouped when IBM, BEA, etc. pay to have their app servers certified. JBoss, since it's free, can't afford that. And who cares? I trust that JBoss works because I deploy EJBs and Servlets written to the standards and they Just Work. If you're in a bigger organization than I am that's spending $millions on your infrastructure so you don't just trust JBoss out of the goodness of your own heart, you have two options. 1)Test it yourself or 2)Pay IBM or BEA or someone else because they certify that they've tested it for you.

      What exactly is the big problem? Sure, Sun isn't the second coming or anything, but they provide well-written open standards that are unencumbered by patents that open source projects can implement. What the hell is wrong with that?

      --
      If it ain't broke, you need more software.
    3. Re:JBoss is real-world deployable - believe it by Headius · · Score: 1

      I came to my company only recently, so I'm not sure of all the details, but I know the only major problem they've had with JBoss is the lack of clustering/failover. The simple solution here has just been to run more JBoss instances (they're really friggin tiny) to cover all the bases. Performance has been great (not the best, naturally, but really top-notch), and ease of use is phenomenal.

      Personally, I'd say my biggest complaint is the available documentation. Even the for-sale docs aren't all-inclusive, and the free ones can be maddeningly vague. There are, however, many other sources for install and config information. The lack of complicators like a separate deployment tool (e.g. ejbc) or unfriendly supporting descriptors make documentation less of an issue.

      And of course, we all know how helpful full source can be...I don't know how many closed-source Java programs (puh-lease, that's like closed-source HTML pages) I've had to decompile to figure out what their hacked-up code is doing wrong...

  31. Re:Java vs Apache, its an easy decision. by Anonymous Coward · · Score: 0

    Someone didn't get their oatmeal this morning and is feeling a little "backed up", huh?

  32. Re:Java vs Apache, its an easy decision. by fantastic · · Score: 1


    "Well sorry suckers but in my local book stores, the amount of shelf space on Java books is heading down and thats a sign that the language has gone the way of Ada, Pascal and others. I figure Java books will be very hard to find in 5 years if not impossable."

    And how many books are there on C in your local bookstore? 1? Looks like no-ones writes in C either then. The great thing about Java is all the free documentation and tutorials. It is probably the most written about language ever.

    "One of the major supporters of Java at sun is Bill Joy. Keep in mind that this is the person that created the vi editor."

    Wrong editor, wrong guy. James Gosling and Xemacs

  33. C# Apache Jakarta ports: NAnt, NUnit, Log4Net by Anonymous Coward · · Score: 3, Interesting

    Sun should watch what they're doing with Apache or people may leave the Java train in favour of C# which may be perceived to be more open with the Mono project. It is really easy to port Java code to C#. Mono is getting better and better every single day. People have already independently ported Ant (NAnt), JUnit (NUnit) and Log4J (Log4Net) to .NET.

  34. WebSphere considered harmful by toriver · · Score: 1

    Well, since people who use other containers than WebSphere and/or write their apps more in line with modern ideas (read "Core J2EE Patterns") rather than old ways of using lots of entity beans (which is bad) don't have all those problems...

    I wish fans of "competing" technologies would find a way of actually say what's better with their way, instead of wasting their time posting FUD about how their mis-use of a technology means the technology is at fault.

    1. Re:WebSphere considered harmful by alext · · Score: 1

      J2EE patterns, specifically the EJB patterns, are really just putting lipstick on a pig, as they can't hide the underlying problems with reentrancy, locking, consistency, DB roundtrips etc. endemic to EJBs. This isn't a WebSphere problem by any means, I'd guess that IBM is better placed than many to develop a way out, at least for DB/2 users.

      Personally I recommend TOPLink, either with or instead of EJBs, to get rid of the most annoying aspects, I expect other persistence frameworks could help as well.

  35. Re:Java vs Apache, its an easy decision. by Capt_Troy · · Score: 2
    Hey Thogard-

    I use VI as well. I've programmed in C/C++ for years and am currently working on a Java project today.

    I don't think you can relate the number of books on bookstore shelves to the popularity of the language directly. Java has just come out (compared to C and the older languages) and so like any other new thing, tons of worthless books were written to take advantage of the "Newness factor". Those worthless books are being weeded out and only the worthy will survive, thus the numbers of "Java for Dummys" type books will go down and we'll be left with the few quality books that are really out there, same as it is with most of the C/C++ text today.

    I'd say that I am equally experienced with both Java and C and C++. I'd go with C++ any day for most projects, and I wouldn't be sad if I didn't have to do any Java anymore. But I do think it has a purpose, mostly related to serverside web based stuff and web based stuff in general. But it's just another choice, you can do the same with PHP or Perl etc.

    So why is sun fighting with Apache? Who knows, but I appriciate all the work the Apache group has done for us and I think Sun is way off base here. They should concerntrate on building up the fortifications for the oncoming .NET vs. Java war. Better to hava Apache as a friend than a foe in that battle. -T

  36. Re:Apache/Sun (time for the lawyers) by fitten · · Score: 1

    Yes. Most programmers have to sign a non-conflict of interest agreement when they are hired. If you work for IBM and also help develop a competing product on the side, then you are in Conflict of Interest (honestly whether or not you signed the agreement, imo).

  37. Re:Java vs Apache, its an easy decision. by Anonymous Coward · · Score: 0

    "One of the major supporters of Java at sun is Bill Joy. Keep in mind that this is the person that created the vi editor."

    Wrong editor, wrong guy. James Gosling and Xemacs


    What are you talking about?
    Bill Joy wrote vi and is also a major supporter of Java at Sun, you idiot.

  38. Re:Who cares? by Brummund · · Score: 1

    Furthermore, J2EE is NOT a web server, but a aplication server.

    Actually, it's a set of APIs and specifications for things considered "enterprise".

  39. Re:Java vs Apache, its an easy decision. by Anonymous Coward · · Score: 0

    Jeepers H. Crackers -- why does FUD like this get modded up? How is this insightful? Good for you for ranting against Java (and getting some of it wrong by the way). It would be great if people read the moderator guidelines occasionally and supported things that could be defined as "interesting" and not "what I agree with."

  40. Sun be Java monopoly? That's UNPOSSIBLE! by Anonymous Coward · · Score: 0

    with due credit to Ralph Wiggum.

  41. C'mon little fishies! by Joseph+Vigneau · · Score: 1

    Nice troll!

    1) Java v. C and C++ and cyclone(?)
    2) vi v. the world

    I'll allow the other replies to your post to blow the chaff off of this one..

  42. JavaFaces? by krulgar · · Score: 2, Interesting

    I currently building a few applications using the Struts framework (I assume that's what was intended in the original post "stuts") and I've been really happy with the Jakarta efforts (including ant and log4j).
    I have not read about JavaFaces, nor could I find anything obvious on java.sun.com. If anyone has a bookmark for a good summary page or two, would you mind posting them?

    1. Re:JavaFaces? by municio · · Score: 1

      http://www.theserverside.com/resources/article.jsp ?l=Portlet_API

    2. Re:JavaFaces? by Anonymous Coward · · Score: 0

      You could try searching google.

      It claims to be a GUI framework for JSP pages (I assume it would abstract away the details of parameter passing, server side method invocation and the like). The community draft isn't even available yet though, so it will be a while before it's being used.

    3. Re:JavaFaces? by krulgar · · Score: 1

      I did search google, and I found a few different sources for "JavaFaces" and it wasn't clear that they were all the same.

      The point of the original post is the dissonance between Sun Micro and Apache/Jakarta, so why is this alternative (read "non-Sun") competitor of Struts listed as an issue in this dispute? THIS is why I thought I might be missing something.

      Coward - thanks for posting the link to google, I'm sure I couldn't get there on my own.

    4. Re:JavaFaces? by germuska · · Score: 1

      Struts and Java Server Faces are not "competitive". See the Struts FAQ They do different things. Struts is mostly a controller (with some nifty view components). Java Server Faces is supposed to develop a GUI for creating view components (JSPs).

      At least a few major Apache contributors (Craig McClanahan, James Strachan) are involved with Java Server Faces...

  43. Keep in Mind by Greyfox · · Score: 4, Insightful
    IBM and Sun are competitors. Currently, IBM is using Open Source Software to undermine a couple of thorns in its side -- Sun and Microsoft. To a lesser extent, it could hurt Oracle as well (IBM sells DB2, which competes with Oracle, you see.)

    There are a fair amount of Open Source enthusiasts inside the company. Many of them used to be OS/2 enthusiasts, and you remember what happened with that product the moment some marketroid thought it might be inconvienent to keep producing it...

    What I'm saying here is IBMs advocacy of Open Source Solutions is not in the least bit altruistic. They will continue to be our "friend" as long as they can make money off what we do. The minute that is no longer the case, they will drop us like a lead balloon. If things get really tough, don't expect them to stand by us.

    --

    I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    1. Re:Keep in Mind by Anonymous Coward · · Score: 0

      And if they leave, we still have their code. So where is the loss?

    2. Re:Keep in Mind by ScepticalTech · · Score: 1

      Do we? What if they turn off DB2 on Linux?

  44. GPL Java Replacement by bwt · · Score: 2, Insightful

    The open source community needs to release a GPL version of Java. There are innumerable projects out there all of which have struggled independently to get to partial JDK 1.1 capability.

    Until there is a highly competitive GPL java compiler with a full set of foundation classes, nobody should be happy about using Java because it is essentially proprietary technology.

    Between GNU Classpath, gcj, jikes, KOPI, Kaffe, Japhar, and a dozen others, its amazing that Sun is so far ahead of what you can do with pure GPL.

    1. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      I wonder why Transvirtual's Kaffe Java VM development basically died. I think it is due to the "almost free is good enough" nature of the Sun JVM. I guess Sun will have to start charging for the JVM - they will have to eventually when Linux erodes their hardware revenue. Kaffe will experience renewed activity only at that point.

    2. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      If I remember correctly, Transvirtual took some $$$ from Microsoft and implemented J++ extentions into their JVM. That pretty much killed them in the open sores community.

    3. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      The GPL Java Replacement shouldn't be Java at all.
      The Java language should be replaced by a higher-level, dynamically typed, object-oriented
      language like Ruby or Python. The "Java platform"
      is unnecessary. Ruby/Python already run on Solaris, Linux, and Windows -- with Python available for the Java JVM and .NET and Ruby with a Java implmentation that will soon generate JVM byte-codes as well.

      Beyond that, the Free Software community may ultimately be able to ditch both the JVM and .NET in favor of the parrot project's byte-code interpreter or (perhaps even better) a gjc-like front end to the gcc complier.

      I wish the Free and OSS software communities would put the energy being wasted on Java and .NET into our own GPL-ed platforms.

    4. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      > I wish the Free and OSS software communities would put the energy being wasted on Java and .NET into our own GPL-ed platforms.

      They are

    5. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      You seem to have missed the obvious fact that open source development is incapable of creating anything complex. Open source imitates at best, but normally isn't even capable of going beyond alpha quality imitations.

    6. Re:GPL Java Replacement by Anonymous Coward · · Score: 0

      mod this up!

    7. Re:GPL Java Replacement by knewbee · · Score: 1

      Why? I guess, by a strict definition, Java is a proprietary language. If you really need to modify Java for your particular purpose, you can. The source code comes with the jdk download. The problem that Sun is trying to avoid is one where you have many different versions of Java. (sans releases of course) I would hate to develop an application that I had to write specifically for a targeted Java implementation. It sort of defeats one of the purposes of the language. What are you suggesting the problems with Java are? Or is it voodoo soley because it is "proprietary?"

  45. Re:Java vs Apache, its an easy decision. by hey! · · Score: 3, Funny
    It sure as hell isn't os class language and its not a language for amature programmers (because VB wins that one).


    Hmm, so you don't see any need for a programming language between those extremes? I would infer your position is that people who aren't creating operating systems (by that I mean the software that sit between the iron and everything else) are amateurs?

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
  46. Daddy, Why is Sun so mean to Apache? by Anonymous Coward · · Score: 3, Funny

    Dad: 'cause they're a Java monopoly, Sally. Apache's truly open software threatens to hurt Sun's bottom line.

    Sally: Sun are mean bullies! They should leave Apache alone!

    Dad: Heh heh, yes they should Sally, yes they should.

  47. Re:Java vs Apache, its an easy decision. by fantastic · · Score: 1

    James Gosling designed Java and is still involved in its design. You can't get any more major than that.

    Bill Joy was/is a major supporter of jini/jxta.
    Java draws more from xemacs than vi, I prove my point

  48. Sun loves JBoss by skelf · · Score: 3, Informative

    Marc Fleury of JBoss (at an informal session in Boston last month) said that he is in constant contact with developers and management at Sun, and that Sun secretly loves JBoss, because grass-roots projects like that are just what Sun needs in their fight against M$.

    I also remember him actually defending Sun's charging so much for J2EE certification, but I can't remember what his reasoning was.

  49. Re:Java vs Apache, its an easy decision. by Frank+Sullivan · · Score: 5, Insightful

    Why flamebait, when you can throw fresh chum with no nasty hooks in it? :}

    "From what I've seen, Java sucks". Does this mean you've never actually programmed in it?

    ALL high-level computer languages, even C, are "hand holding". That's the point! I want my language to make my life easier by hiding the gory details, and i will use the highest-level language that can possibly work well for whatever i'm doing. In many cases, that will be Java.

    If you want language-bashing, C++ is a horror. Someone please tell them that you can't solve every problem by adding a new keyword. And if you want to bring up yacc (and by extension, LALR parsing), Java is as clean as C. C itself isn't pure here... try this statement: 'if(a) if (b) something(); else something_else();' Legal C, with a shift-reduce conflict. Does the else apply to if(a), or if(b)? You DID read about LALR parsing in detail, didn't you? But that pales in comparison to C++, which simply cannot be parsed without dynamic type information in the parser. See Knuth's one-line crushing criticism of in in DDJ a few years back. But i digress.

    Counting books on the shelf for a language is NO measure of its success, because most computer books are crap. The bad ones are dying off. I keep exactly two C books on my shelf - K&R and Plauger. Does this mean C is dying? No, it means those two books are so effective i don't need anything else.

    As for VB... it's not a language for programmers who need hand-holding, because it's saddled with that horrible BASIC grammar that will do nothing but get in their way. If you want a language for beginners, check out Python. The worst thing about using it for a student language is that the students will be grossed out the moment they have to learn a bloated monster like C++ or Perl (not knocking Perl, it's my favorite language, but Python is better).

    Java reminds me a lot of Unix... it's not perfect by any stretch, but it's so dang good that there is little point in trying to do better. Its utility as a lingua franca outweighs its minor shortcomings. The nicest thing i can say about Java is that i hardly ever come up against limitations of the language itself - if i have a language-level problem in Java, it is usually due to my own ignorance, especially ignorance of its excellent libraries.

    Okay, i'll stop now.

    --
    Hand me that airplane glue and I'll tell you another story.
  50. Re:Java vs Apache, its an easy decision. by thogard · · Score: 2

    The number of C books is slightly more than there were 10 years ago. we have the classics of K&R C, The C answer book, The Unix programming env and a large number of other worthless titles. Compare that to Pascal books. There are now 3 at the local Borders. How about Ada, also less than 5 but a decade ago ranked more shelf space than java and C# combined. Most of the Java space has been reallocated to C#. To me that means its as trendy as the wrong color skirt at a fassion show.

    Bill Joy might be James Goslings boss considering Bill is a founding member of Sun and Chief Scientist and Corporate Executive Officer while James can't even seem to mention his title on his Sun Labs web page

  51. Not Sun specific by PierceLabs · · Score: 2, Insightful

    This isn't a Sun problem specifically - all of the companies that were using OSS to gain marketshare are wrestling with it now. Some of them have blamed Sun (Lutris) for their own inability to make OpenSource work for them. The simple fact remains that no company that needs to make profit in order to stay in business can cater to open source in the same spaces where they are trying to make money. Sun has open sourced Star Office, no biggie - doesn't make them any money really. Sun won't give away or disrupt J2EE license revenue to cater to open source because they make money from this. Anyone who doesn't understand this and thinks that Sun or any other company can just give this stuff away really needs a good class in economics and finance.

  52. Why Sun dislikes Apache. by supabeast! · · Score: 2, Insightful

    For all of the conspiracy theorists creating ludicrous examples of why Sun doesn't like Apache, let me put this into simple, obvious terms:

    Now that AOL has given up on selling iplanet as a webserver (Apart from other things.), Sun is still trying to make money off of it.

    Apache is iplanet's biggest competitor. Apache is free, more popular than iplanet, and considered by many people to be better than iplanet.

    Every time someone runs apache on Solaris, Sun sees that as another iplanet sale lost.

    Need any more details?

    1. Re:Why Sun dislikes Apache. by pmz · · Score: 5, Interesting

      Every time someone runs apache on Solaris, Sun sees that as another iplanet sale lost.

      Then why did Sun package Apache as part of the default install of Solaris 8?

      Solaris now ships with Apache, Perl, and Java. Out of the box, it is a pretty potent web-serving OS. And it can be downloaded for free or delivered to your front porch for about $50US (only Free operating systems are more cost-effective; M$ Windows doesn't even come close).

      iPlanet is expensive enough that it really doesn't compete with Apache directly. Typically iPlanet is used in "enterprise" environments alongside J2EE and Oracle. When a company can throw a ton of money at a big server and Oracle, iPlanet is just the icing on the cake.

    2. Re:Why Sun dislikes Apache. by haggar · · Score: 3, Insightful

      I think you are being too simplistic. I wonder if you know that Apache webserver is part of every standard Solaris 8 installation. That's right, every bloody box with Solaris 8 running on it, has Apache installed. All you need is load the httpd.

      And, if Sun had all that dislike for Apache, why would it cooperate with the Apache people on Tomcat? Without Tomcat, Apache would be useless to at least half of the customers. Yes, servlets are -that- important. And Sun helped Apache get it's own servlet container, in a big way.

      I know that simplification allows for more Karma, but I appreciate intelligence more. I am sure you can figure out an intelligent version of your post, too.

      --
      Sigged!
  53. Re:Who cares? by Anonymous Coward · · Score: 0

    things considered "enterprise"

    Whatever the fuck that means. Ususally stands for "one or more of bloated, overcomplicated and insanely expensive".

  54. Re:Java vs Apache, its an easy decision. by Anonymous Coward · · Score: 0

    You're probably one of those cheese-eating surrender monkies who doesn't like pointers. :)

    C is the mothertongue, I tell you! :P

    Amusement aside, I agree with the bulk of your statement. C has been around forever, there've been tons of C books, and tons of reviews on them. Only the best have survived.

    VB.. I don't think VB is for programmers, as much as it is for dabblers. VB is great for people who want to whip up a quick application to do something simple, with little amount of hassle. For people learning how to program for a living, though, it's a major obstacle. It really isn't similar to much aside from.. Well, basic. On the other hand, if I learn C, I can apply a lot of that knowledge to C++. If I know either of those, Java's not going to be nearly as hard to pick up. Et cetera, et cetera.

    Frankly, I wouldn't use Java unless it was required (Which it is, because of my current java classes. Yea, I want more bloatage after my name. *chuckle*).. But, it's a great language to have around, because if you can't do something in some other language, you almost certainly can with Java.

  55. Re:Really necessary for a big Sun stamp of approva by jilles · · Score: 2

    Yes, the compatibility test suite is a really good one being allowed to say you passed it (by carying the compatibility logo) is quite different from spreading the rumor that software package is generally believed to be compatible.

    Effectively SUN is using their monopoly position (regarding the compatibility tests) to selectively grant licenses to market partners. IMHO the market should be open and anybody (including MS) should be allowed to attempt to pass the requirements (not necessarily for free).

    --

    Jilles
  56. Amen, and Sun is doomed by Ars-Fartsica · · Score: 3, Interesting
    Good post, and on top of the bad will they are creating, Sun is doomed in the market.

    Linux is peeling away their low end (notwithstanding their effort to derail the linux rack market by buying and then effectively scuttling Cobalt), and IBM is shaking down their top end.

    Microsoft continues to confound Sun, even as McNealy turns up the vitriol. Scott - let me make this brief - you cannot beat Microsoft. Stop trying. Take a lesson from Steve Jobs - play nice or route around them, but don't try to take them on directly. They're tougher and wealthier and more influential than you.

    Hardware is getting cheaper, and software is becoming a commodity. Services are the last high margin business left, and Sun isn't a big player.

    1. Re:Amen, and Sun is doomed by pmz · · Score: 1

      IBM is shaking down their top end

      This is arguable. IBM has failed to gain market share against Sun's Enterprise/Fire servers, and IBM's servers tend to not offer better price/performance. Also, IBM's server lineup is heavily fragmented between UNIX/RISC servers, mainframes, and Windows NT.

    2. Re:Amen, and Sun is doomed by Anonymous Coward · · Score: 0

      Not only is it fragmented, but IBM's solution to problems is to support everything in that the customer keeps throwing money at them until the problems are solved, or the customer runs out of money. IBM will even offer really cheap hardware to get into this sort of deal. Sun on the other hand sells really expensive hardware, then is hands off from then on (except for hardware/OS support). The customer is expected to know what to do with the hardware they have.

      IBM is a solutions company, while Sun is a hardware company at heart. Overall, Sun is cheaper, if you have good admins at your company, who know what they are doing. Sun is sort of looking like they are following in the footsteps of IBM here, for their future direction, though.

      Hopefully Sun will unbend on this... there are still a lot of people in Sun who love working with and using Apache. Sun needs to stay with what it does best... being a hardware company.

  57. Who CARES about certification? by revscat · · Score: 1, Flamebait

    I am sure that everyone here has met an MCSE (or other certified) bonehead who passed the tests but couldn't do system administration in a real world setting to save his life.

    Now admittedly Sun's requirements for J2EE certification are a bit more stringent than those required for becoming an MCSE. But certification can only get you so much. The proof is ultimately in your product. JBoss has received so much attention lately because it is a solid, robust product. The attention paid to its lack of certification quite simply distracts from this.

    Certification is a way for Sun to revamp costs. I don't have a problem with that at all. Lack of certification for JBoss probably means that it won't be used on many enterprise systems for the time being, but that will (and is) changing as it continues to evolve. In the meantime, JBoss will succeed or fail in the marketplace on its own merits. And if and when it does reach "critical mass", it will be all the sweeter because this will have been an uphill battle for the entire JBoss team.

    - Rev.
    1. Re:Who CARES about certification? by Anonymous Coward · · Score: 1, Interesting

      Pretty simple... if you have an old-line IT manager who went to the "nobody ever got fired for buying IBM" school of management, it's a heck of a lot easier to sell an open source project if there's certification to ease his fears.

    2. Re:Who CARES about certification? by arunkv · · Score: 1

      I think you are confusing certification of individuals on a certain programming language or platform as opposed to certification of an implementation of a spec. The MCSE, Sun Java Developer and other certification programs exist to certify an individual's skills. The JBoss issue is about certifying JBoss' implementation of the J2EE spec.

    3. Re:Who CARES about certification? by Mr.+McD · · Score: 1

      Well said. A friend of mine was trying to get me to get "Java Certified" by Sun because you only needed a 70 on the test to pass. Go figure.

    4. Re:Who CARES about certification? by jhunter · · Score: 1

      Certification is *not* optional in the JCP.

      Sun's legal position is that the specification itself constitutes IP and that you as an implementor must license this IP to create an independent implementation. The terms of that license (among others) are that you must run and pass the TCK compatibility test kit. The TCK may cost tens of thousands of dollars or more. But you must are required to pay if you're going to implement the specification.

      It's a brilliant legal hack. Whether or not it's a strong legal position we won't know until a case comes to court. I presumably JBoss is allowed to keep shipping because Sun would rather not use them as the test case.

    5. Re:Who CARES about certification? by Anonymous Coward · · Score: 0

      Actually, you only need a *60* to pass, but don't let that fool you. It's a bitch of a test. It took me twice to pass it, and I've been doing Java for a year and a half. It was a suprisingly difficult test.

  58. Sun won't provide the Compliance Test Suite by Anonymous Coward · · Score: 0

    J2EE compliance requires passing the "Sun J2EE Compliance Test Suite". You have to be a paid licensee in order to see/use it in full. (There's like 100 of the 3000 tests available via the SCSL, but the full kit is only from them.)

    They won't even let college students or other academics use the CTS for research purposes.

  59. The Java certification is so cheap. by Petrus · · Score: 4, Insightful

    I think, that lot of people are unjust casting curses to Sun. It was sun who donated most of Netscape (Mozilla), most of StarOffice (OpenOffice)and other things such as OpenLook even before Linux begun.

    Whether it would happen or not, they have the right to be careful about Java spec incompatibility. Perhaps it really does cost $50k to certify it. While $50k might be a lot for Apache, it is only some 0.005% of what IBM pledged to invest to Linux. Why do not some commercilal vendors team up with IBM to foot the bill for the Apache Java?

    Disclaimer:
    I have no afiliation with Sun whatsoever. I jst watch what is happening. Sun just gives out great software and reaps wrath. IBM is all promisses and is praised all over Linux "community".

    1. Re:The Java certification is so cheap. by Derkec · · Score: 2
      When you said 'before linux began' I think you meant the more recent widespread adoption of Linux and particularly IBM's involvement? But yeah, I think for being a big company, Sun does decent things for open source. They released OpenOffice which has potential for competing with MS Office. Java is controlled by a community process not changed by the whim of McNeally or Joy. Recently they've pledged to help out in the Linux kernel. While they don't have 1 billion to give out, McNeally did go out on stage dressed up as Tux, which you'll never see Lou do :) So if they percieve that XML and logging are critical and supply that to the their users instead of forcing their users (who might not all know what Apache offers) to go find tools, are they really doing anything wrong? Maybe, but it's a hard call for me. The J2EE certification issue concerns me but I'm interested in what Sun has to say about it. Oh well.


      Disclaimer: I have been employed by Sun, although temporarily. I personally like the company, and might be badly biased. I don't think so though.

    2. Re:The Java certification is so cheap. by Petrus · · Score: 1

      Good Point.

      They are certainly very generous and straightforward, although they don't play the soft of new Open Source politics well. Perhaps they don't want to.

      When I said "Before Linux begun", I was referring to the OpenLook windowm manager (olvwm) and developement tool, that I was using in 1990 (Linux started in 1991) and that was never surpased as by neatnes and configurability by any GTK+, gnome or qt in neatnes and configurability, that was based on Athena widget set. I mean that one, which is not shipped with any mahor Linux distribution since 1997 and which WxWindows are stopping to support.

      It had quite nice, oval-shaped windows, wery neat graphics. E.g. the "stic-it" pins on the window, found only on KDE/gnome decade later were casting pin-shaped shade. The windows poping was neatly animated - on 30MHz 68030.

      It was atop of Athena Widget set, where every GUI item could be custom colored/fonted/sized... by 'editres' athena widget editor. That is something you won't see yet on gnome or KDE.

      Well, you know, we are slowly going backwards, limiting the capabililities of Linux, altil the Linux PC will be as arcane and unusable as Windows.

      More on Open Look:
      http://sunsolve.sun.com/data/802/802-5329-1 0/pdf/0 1.framenewnew.pdf
      http://www.vmlinux.org/xplan/

    3. Re:The Java certification is so cheap. by Anonymous Coward · · Score: 0

      It was sun who donated most of Netscape (Mozilla)

      Not so. The Mozilla stuff was mostly in place before iPlanet was officially formed (4/1999). The stuff that was contributed to Mozilla after that (LDAP SDK, NSPR, NSS, etc.) was done by Netscape people who were still Netscape employees working at iPlanet.* In fact, Sun still has many many problems with using the Mozilla code. I have a friend at Sun who works with a lot of the Mozilla code and uses it as much as possible with iPlanet/Sun products. He gets a call from a different lawyer every week asking him about the legality and licensing issues involved. In this case, it appears that Sun Just Doesn't Get It.

      *Almost all of these people who didn't leave to join startups came back to Netscape/AOL after the dissolution of iPlanet.

  60. Re:Java vs Apache, its an easy decision. by Frank+Sullivan · · Score: 5, Insightful

    Oh, i like pointers. I like high-powered handguns too, but i wouldn't use them to settle ALL my social problems! Pointers are fantastic where precise memory control is required. Precise memory control is NEVER required, except for systems programming. Something like the Linux kernel should absolutely be written in C. Something like the typical business app has no business whatsoever using C. And yes, C is the mother tongue. Any professional programmer that doesn't at least understand it is severely ignorant, even if they never use it.

    I wouldn't even say VB is for dabblers. I'd say it's for morons, and the poor victims who are forced to use that wretched excuse for a language. The only decent part at all is the IDE, and there are better ones.

    I don't even think much about the language anymore... my programming these days is abstracted away at the problem and architecture level, and the language is just a side point, as it should be. That's why i want my language to get in the way as little as possible. C often gets in the way, due to its crude libraries. I find Java, Python, Perl, SQL, and Unix shell to be my languages of choice.

    --
    Hand me that airplane glue and I'll tell you another story.
  61. SUN==MICROSOFT by nuetron · · Score: 0

    SUN==MICROSOFT really

    1. Re:SUN==MICROSOFT by jameslore · · Score: 1
      Shouldn't that be:

      Corporate sun = new Corporate();

      if (!sun.certify("JBoss") || !sun.support("OSS")) {
      sun = new EvilEmpire();
      }
    2. Re:SUN==MICROSOFT by Anonymous Coward · · Score: 0

      public static EvilEmpire newEvilEmpire() {
      if (Math.random() * 100 > 50) {
      return new Microsoft();
      }
      else {
      return new Sun();
      }
      }

    3. Re:SUN==MICROSOFT by Anonymous Coward · · Score: 0

      Think more like EvilEmpire() extends BigCompany()

      does that sound backward? :)

    4. Re:SUN==MICROSOFT by MillionthMonkey · · Score: 2

      No wonder I think they're evil.

  62. JBoss certification fund by Anonymous Coward · · Score: 0

    So, why doesn't JBoss group start a certification fund, tax-deductible, to raise money for thier certification? As many businesses out there are saving huge fees by using it, I think they could make a reasonable case that at least a few of them, or just the general coder public, ante up a few hundred dollars each...How long could it possibly take to raise the funds?

  63. Go-Mono! by Mr.+McD · · Score: 2, Flamebait

    If Sun's antics are making you ill, why not help out the folks at Ximian on Mono? It is backed by a REAL ECMA standard and not controlled by one company. Sure it's based on an MS product, but at least MS had the balls to submit it to a standards body and NOT retract it.

    1. Re:Go-Mono! by alext · · Score: 1

      You guys never give up, do you?

      New readers should start by ploughing through earlier Dotnet discussions, where the usefulness of ECMA's standardization the CLR and a minimal set of classes (around 10% of the total platform) was shown to be nil.

      Miguel should stop chasing something he can never catch and instead join a VM project that can help unify open source efforts rather than fragmenting them further. "Parrot" wouldn't be a bad start.

    2. Re:Go-Mono! by Mr.+McD · · Score: 1

      Whatever.

  64. Re:That's what happens with proprietary "standards by Anonymous Coward · · Score: 0

    Well, in other fields, there certainly is - here's the SAT version:

    Mesa is to OpenGL, as
    Ghostscript is to Postscript (and PDF), as
    GNUStep is to OpenSTEP(Mac OS X), as
    gcj and guavac are to Java-the-language, as
    Classpath is to Java-the-library-set, as
    Kaffe is to Java-the-VM, as
    JBoss is to J2EE.

    All those products have substantial numbers
    of users... So yes, there is a point...

  65. You said a lot. You said nothing. by Anonymous Coward · · Score: 0

    As for the shift-reduce conflict - what the fuck does that have to do with _anything_?
    Look at your bizarre line of "reasoning":

    - Java is a wonderful high-level language
    - Java is as clean as C.
    - C++ shares C's sytax
    - C++ has shift-reduce conflict with "if" and is bad

    Then by your own reasoning, Java has these same conflicts and is also bad.

    You then go on to bitch about perfectly legimate languages (Python and VB) for the same reasons you flamed the parent poster for! You have obviously NEVER PROGRAMMED IN THOSE LANGUAGES!

    Hmmm. I see. Jabber pointlessly about any number of incorrect "facts" and get modded up to "5". Interesting. Pandor to the egos of the Slashdot self-appointed language experts.

    Hypocrite.

  66. Java for Dummies by Anonymous Coward · · Score: 0

    "Java for dummies" shouldn't be the name of a book.
    It should be a definition. Something like:
    "Java? For Dummies!"

  67. Lessons not learned by augustz · · Score: 4, Insightful

    We see companies who promise open source (as sun did for years) or open souce friendliness (as they still do) without actually changing anything in terms of licensing. This has happened to tons of projects, not just with Java. The fact is, listening to the Java Lobby claim something will be an open standard does not make it so. We have standards bodies and the OSI for a reason. Unless it is submitted to one of them or licensed with an OSI license, caveat emptor.

    This comes as absolutly no suprise to me, and I actually don't have huge amounts of sympathy for Apache, after all, Sun appears to be well within their legal rights.

    Despite the anti-microsoft zealots out there, Sun is not the knight in shining armor, but a company that has very cleverly exploited open souce development without being open source, and one which I am convinced would pull every closed source trick in the book in a hot minute if they thought it would benefit them.

    It is staggering, the Apache group has been doing huge amounts of work to make Java a standard, ignoring the fact that the only J2EE Java standard comes from Sun.

    I for one have steared clear of Java for precisely this reason, if it is not a standard there are some clear business reasons why you want to avoid it unless you like having the rug pulled out from under you periodically.

    1. Re:Lessons not learned by Petrus · · Score: 1

      You wrote: [Sun] very cleverly exploited open souce development

      Do you remember where from do we have:
      --- Open Office?
      --- Mozilla?

      These are not only some Linux applications, these are major competitive Aces against omnipresent Monopoly. These far the only ones.

      More quiz qiz questions:
      --- Who coded Athena Widget set?
      --- Who donated OpenLook souce 11 years ago?
      --- What is XIL imiging library?
      --- What other company is opening source as much as http://www.sun.com/software/communitysource/ ?
      --- Which other Linux vendor open as much of i386 kernel code as Sun for Solars?

      What I see clearly is the ingratitude is the World's recompense. Do slanderers have the courage to put foot where their mouth is?

      Petrus

    2. Re:Lessons not learned by augustz · · Score: 2

      Petrus

      Slander is a legal term, and under current US law puts me in legal (and therefore financial) jeopardy. And this, simply for stating my opinion.

      I think you'll find that in the open source world, folks enjoy the right to have their own opinions, free of the legal armwaving and hassle that folks like yourself, and plenty of big corporations employ. Open source is not simply about free software, it also is concerned with freedom.

      You also happen to be wrong: Unless you see a license listed as OSI approved, it is unlikely to be really open source. Folks need to remember:

      Shared Source != Open Source
      Community Source != Open Source

      There are incredibly important distinctions between these.

      Notice which term appears in that URL you are bandying about:
      http://www.sun.com/software/communitysourc e/

      And the Mozilla code base? Check your timelines.

      Respond to folks who start claiming things are slander or defamation is usually a waste of time I've found. That kind of approach is bogus in almost any situation, but on mailing lists and places like Slashdot it is really sad to see. If you think you have a case for slander I'd advise you to hire a lawyer and sue. Otherwise, why not post elsewhere.

    3. Re:Lessons not learned by Anonymous Coward · · Score: 0

      You sir, are a spectucular fool.

    4. Re:Lessons not learned by Petrus · · Score: 1

      Nothing about law here:
      Slander \Slan"der\, v. t. [imp. & p. p. {Slandered}; p. pr. & vb. n. {Slandering}.] 1. To defame; to injure by maliciously uttering a false report; to tarnish or impair the reputation of by false tales maliciously told or propagated; to calumniate.

      I wish that people in their zeal keep in mind, that although they have right to opinion, they should think thrice about expressing it if that opinion may cause injury to someone's reputation.
      The harm is lot easier done than undone.

      If people won't learn this (not only on slashdot), they will ham popple with good intentions, alienate lot of observers and destroy good projects.

      If you compare it to OSI advocates, they are no less willing to compromise the Open Source definition than SUN is willing to change their stance on Java Certification.

      And now, compare, all SUN wants is that the term "Java" not to be used on fully non-comptible products, something that successfuly stopped Microsoft from embracing, extending and hijacking it.

      What's in a name?
      "Open sourcing", in turn, requires lot more from the donor than free use of a name.

    5. Re:Lessons not learned by augustz · · Score: 1

      Perhaps check the law as well? It's very clear, slander is actionable for damages, and has a clear and specific legal meaning. Before running around claiming slander, perhaps have a clue about what it means (though if English is your second language I understand, just consider flaming less).

      The question of Java trademark usage is orthoganal to the question of whether community source == open source. It does not, and you are trying to confuse the issue.

      OSI exists to protect everyone from folks trying to pretend to be open source.

      Sun's community source exists only to protect itself.

      "all SUN wants is that the term "Java" not to be used on fully non-comptible products"

      Have you even CHECKED to see if JBoss is "fully non-compatible".

      Petrus, you DO NOT HAVE A CLUE about what you are talking about, even on this totally tangential stuff. PLEASE, before opening your mouth again, READ the JBoss/Jakarta mailing lists and Apache's position paper.

      What JBoss and others want to be TESTED and SHOWN to be totally, 100% compatible. Please provide evidence they are totally non-compatible.

      There's a saying you should consider. Better keep quiet and be thought a fool then to open your mouth and remove all doubt.

    6. Re:Lessons not learned by TheAJofOZ · · Score: 2
      You also happen to be wrong: Unless you see a license listed as OSI approved, it is unlikely to be really open source. Folks need to remember: Shared Source != Open Source Community Source != Open Source There are incredibly important distinctions between these.

      Okay, here's an interesting thought that just sprang into my head. If Java is not a real standard because it only comes from Sun and not a standards organisation, then why is opensource a standard (standard definition of the term opensource at the least) when it is completely controlled by the OSI?

      I don't mean this as a flame or troll, but who decides who gets to be a standards organisation? People argue that if Sun were to collapse (or just abandon Java) then the Java "standard" would become worthless and the Java developers would be left high and dry. What happens if the OSI for some reason collapses (quite possible through some form of law suit which bankrupts them or through a variety of other means)? Wouldn't that make the term opensource completely worthless as a standard?

      The other argument people have is that Sun has full control of Java and that's a bad thing but doesn't this same argument apply to the OSI? The OSI controls the term opensource. If your answer is that the OSI has community input into it's decision making process, so does Java (the Java Community Process).

      I will conceed that the OSI is far more community based than Sun (obviously) but I find it astonishing that noone (including myself) has realised that even non-profit organisations run by community processes can go bad and leave you high and dry. If you want an example of this happening, look at a number of churches (at many levels of the church organisation and please note that this is not a criticism of all churches nor religion etc, just noting the fact that churches can struggle to keep in touch with their aims and can loose their way). I think religion is probably an even tighter binding phenominon than opensource, so if churches can loose their way, what's to stop opensource communities from doing the same?

    7. Re:Lessons not learned by Petrus · · Score: 1

      Yes, english is not my first language. Slander is probably arcane term that remains only in use in legal documents, which probably lifted you up a bit. I apologise. Perhaps 'calumny' would be better expression.

      Yes, a typo. Should read:
      "all SUN wants is that the term "Java" to label only fully compatible proucts". That refers to Microsoft attempted extensions(read context). I have no doubts that JBoss if fully or at least nearly compatible.

      JBoss just wants to be tested. Well, no problem. Sun just wants to do the testing. And it just wants to be paid for the work. Just as I want to be paid for my work. So you can consider us fellows in crime.

      The money is negligible fraction of, say the $1b that IBM invested last year into Linux. How come nobody has a penny to spare? I pledge my $5, a comparable share to my salary as thetesting fees to $1b. Or no, the heck. I pledge $50.

      But by the way, is the "Java" sticker worth the 50 bucks?

      Petrus

    8. Re:Lessons not learned by augustz · · Score: 1

      This is I think an interesting decision. Here's my take on it.

      OSI basically publishes an opinion, that folks can trust or not as they see fit. We trust their opinion because they have a set of principles and mailing list that makes those opinions valuable for others.

      Sun is the designer of a language, Java which they have not standardized or really made open source. Their history is also poor, they've welched on past statements, with credit that's taken as an indication they are more likely to welch in the future.

      Most importantly however, "TCK license is required (not optional) when performing an independent implementation", and it is not clear to me that Sun doesn't have some patent schemes up it's sleave. With sun you are not simply taking an opinion, you are betting your product and pocketbook.

      So yeah, either could go bad, but we only care if Sun does, because they can do real damage.

    9. Re:Lessons not learned by TheAJofOZ · · Score: 2
      So yeah, either could go bad, but we only care if Sun does, because they can do real damage.

      Agreed, but now look at some other standards organisation, say the organisation that certified C# (ECMA?). Wouldn't the same argument apply?

      For the record, I make no claims about the sainthood of Sun, I'm more intrigued as to why standards are seen as infallable when history shows that they quite often don't work out well (HTML anyone - or pretty much any other web standard). Just thinking out loud mainly.....

    10. Re:Lessons not learned by augustz · · Score: 1

      Unless the ECMA has a good history that they are reluctant to lose (I happen to think the ECMA is a bit weak). It means that you can say, this is ECMA standard C# or ANSI standard C, and at some point being able to say that matters more than being able to say, my C is better than your's.

      Initially, Microsoft could clearly make it more important to be compatible with Microsoft, but I think in short order, the standard C# will matter because it will be a base on linux and windows.

      ECMA going bad is a concern, but it is less likely to go bad in Microsofts favor as Sun is likely to go bad in Suns favor, so it adds a buffering layer.

      w3c does patent disclosure which I think is critically important for example and standards are stronger the more it matters to folks. JEDEC now has incredibly strict disclosure requirements so that folks can standardize on SDRAM for example feeling pretty safe in doing so.

      I think it is useful to ask, just how badly can Sun/Microsoft/GPL'ed software screw you if they do go bad? A lot of GPL'ed software allows the FSF to screw them if they went bad, by up-licensing to a BSD style perhaps. Unlikely but possible.

      OpenGFS we see exactly good guys gone bad happening, and it has happend in a bunch of other areas as well.

    11. Re:Lessons not learned by TheAJofOZ · · Score: 2
      Initially, Microsoft could clearly make it more important to be compatible with Microsoft, but I think in short order, the standard C# will matter because it will be a base on linux and windows.

      I think you're overestimating the impact of Linux here as the lack of compatibility with Linux browsers would tend to indicate. However, it raises a good point which I think we'd agree on. While "official" standards are ideal because they are well documented and changes are controlled by some central authority, it is the defacto standard that really matters as a standard is useless if the majority of implementations don't follow it.

      The really interesting thing about that is that it brings us around to saying that it's the implementations that matter and that the official standard holds a very precarious position in the whole set up. If the most popular implementations of Java were to divert from Sun's specifications then Sun's specifications would be worthless. Sun's only protection against this is that they own the name Java (we saw this actually eventuate in the court case between Sun and MicroSoft). The same applies for C# of course, if MS takes the language/system in a direction that Linux users don't like (and Linux actually has enough market share to hold influence) then MS's C# specification will be worthless and Linux will control C# because they control the source to the defacto standard.

      Apologies for treating Linux as some collective company but otherwise the argument gets awfully confusing. Think of Linux in the above paragraph as the collective of developers for Linux's C# implementation.

      ECMA going bad is a concern, but it is less likely to go bad in Microsofts favor as Sun is likely to go bad in Suns favor, so it adds a buffering layer.

      Well, Sun is always looking after their best interests so the concern is more that their goals change, but that's not hugely important. What is interesting is that one of the big reasons the ECMA would go bad is that MS pressures them into it. Further more, because MS controls what will undoubtably be the most popular implementation and the mindshare as to who owns C# (or .Net) with consumers, MS controls the standard regardless of what the ECMA does. The worst the ECMA could do is refuse to allow MicroSoft to call their implementation C# which would have little effect because the general concensus is the .Net is a Microsoft thing not an ECMA thing. MS would not be overly hampered by having to change the name and with the right publicity almost everyone would switch over.

      w3c does patent disclosure which I think is critically important for example and standards are stronger the more it matters to folks. JEDEC now has incredibly strict disclosure requirements so that folks can standardize on SDRAM for example feeling pretty safe in doing so.

      Agreed, patent disclosure is what I am more concerned about than whether a technology is controlled by a company or a standards body. I can keep using any published specification as long as it is patent free and I don't infringe on trade marks. If I want to use an actual implementation then copyright is an issue but once licenced always licenced (for that version and unless the licence specifies otherwise). It's obviously not always pleasant to continue using a technology after it stops being supported but there are all kinds of legacy systems still in use that use technologies that have long since gone out of fashion.

      I think it is useful to ask, just how badly can Sun/Microsoft/GPL'ed software screw you if they do go bad? A lot of GPL'ed software allows the FSF to screw them if they went bad, by up-licensing to a BSD style perhaps. Unlikely but possible

      Risk analysis is always essential, but you need to do it right. Both impact and chance of occurrance as you suggest. However, there is a point where the benefits of a new technology outweigh the risks of it's controller going bad. For each company that will be different I suppose and some people will always be paranoid, others will always be naive and gullable - hopefully we can land somewhere safely in the middle.

      OpenGFS we see exactly good guys gone bad happening, and it has happend in a bunch of other areas as well.

      I guess the only way you can be certain about the direction of anything is to own the intellectual property yourself. If you want something done right, do it yourself.....

    12. Re:Lessons not learned by Anonymous Coward · · Score: 0

      And you can't speel.

    13. Re:Lessons not learned by augustz · · Score: 2

      "MS controls the standard regardless of what the ECMA does. The worst the ECMA could do is refuse to allow MicroSoft to call their implementation C# which would have little effect because the general concensus is the .Net is a Microsoft thing not an ECMA thing."

      This is a judgement call, but I basically disagree. First off, I think Microsoft will continue to support the CURRENT standard very well no matter what, if only for backwards compatability on Windows. This makes it safe to develop to that standard, confident it will run on Windows as well.

      It happens to be that the cool infrastructre parts of Mono are those very parts least likely to change. Class libs are much more likely to change, but very few of them are submitted to start with.

      Java has shown folks like writing cross platform stuff. C# as is is pretty complete as a language.

      The question, what happens when microsoft extends C# and fails to submit to the ECMA. Folks still interested in writing cross platform code will probably be able to do it if they want, which is what I care about. Extensions in core libs don't matter becuase they are not submitted (and can be standardized presumably without microsoft submiting anyways). Infrastructure is unlikely to change.

      It is definatly going to be interesting to see if go-mono.net survives unscathed. That is the clear threat, and Microsoft has to have some legal ammo up its sleave.

      I do think by making C# a true standard, they have a chance with their market share (and if they don't blow it by going legal crazy) to really move us from previous C/C++ standards to a Java like standard but actually standardized. That's a real step forward.

    14. Re:Lessons not learned by Anonymous Coward · · Score: 0

      C# the language is usable (though like Java it's pretty mediocre for an OOPL), but the part of their class library submitted to the ECMA has often been described as too small to be useful by itself.

  68. Re:Java vs Apache, its an easy decision. by J.+Random+Software · · Score: 1

    "New keywords" is an odd complaint about a language that declares abstract methods using "= 0", gives at least three different meanings (non-instance member, no external linkage, not reinitialized at each funcall) to the keyword "static", and resorts to a dummy argument to distinguish prefix from postfix operators.

  69. services key by coltrane99 · · Score: 1
    I would suspect that the main reason for the difference between IBM and Sun in this regard is the difference in their business models. Sun generally seems to try to sell software/hardware packages. IBM tries to sell the software and hardware and also a big wad of consulting to get things started. The consulting is where most of the money comes from for IBM. So they can take the loss on the software itself.

    Perhaps Sun needs to develop a big services organization to thrive. It could be difficult, due to their culture..

  70. Re:Really necessary for a big Sun stamp of approva by aminorex · · Score: 1

    >For large organizations who (like mine) made a
    >$50mil investment in moving to J2EE applications as
    >a corporate standard, the Sun stamp of approval is
    >absolutely necessary.

    Think about *why* certification is
    a checklist item: You want to know
    that your application code will run, to the
    degree to which you have adhered to the
    certified interface contracts. The same goal
    can often be met by using a single revision
    of an open-source solution -- just
    don't upgrade. The certified COTS solution
    and the open-source solution have real cost
    tradeoffs, and I can't comment intelligently
    on how they play in your applications, but
    I do hope for the sake of your organization
    that you will actually analyze and weigh those
    trade-offs, rather than discounting one
    alternative because it doesn't satisfy a
    derived requirement without business
    legitimacy.

    --
    -I like my women like I like my tea: green-
  71. So let me get this straight..... by JohnnyCannuk · · Score: 3, Insightful

    ...the organization that created many projects and librarties that have become the de facto standards in the Web and software industry (Apache Web Server etc) WITHOUT any 'certification' is whinning that Sun won't give away free certifications to open source projects like JBoss?

    This is a tempest in a teapot.

    The crew at JBoss don't seem to think the lack of certification is a big deal and they are in constant contact with Sun. I don't think that is the problem. I wonder what is really bothering Apache? I wish some one would post the REAL reason and not a misinformed link to "J2EE considered harmful" - if you check some of the more java focused sites, you can see that the person who started this rant at Apache doesn't know what they are talking about when it comes to J2EE (because, I suspect, the haven't used it).

    My guess is that this is causing "contraversy" here because it is a great story involving:
    1) Apache, everyone's favorite Open Source organization.
    2) Sun - a corporate Behemoth out to make profits, that is not as bad as but in the same league as, MS.
    3) Java - a favorite target here on /. and cause of many flames. Guarranteed to generate posts - especially from the C/C++/PERL/ groupies
    4) Because of 2) and 3) we also get a bunch of ".Net Vs Java" or "MS Vs Open Source" tangents generated, especially when people bring up the Mono project as an alternative to J2EE.

    In other words, this story gives anybody on anyside of any of /.'s favorite issues an excuse to rant and flame, and nothing else.

    There really isn't a story here. Let Apache and Sun solve their differences like adults without all this sensationalism.

    --
    Never by hatred has hatred been appeased, only by kindness - the Buddha
    1. Re:So let me get this straight..... by nous · · Score: 1
      In other words, this story gives anybody on anyside of any of /.'s favorite issues an excuse to rant and flame, and nothing else.

      well, slashdot is the largest teapot this side of the atlantic, and what we observe is the modus operandi of this venerable institution. since the identities are hidden and the possibility of an eternal archivist ( unlike usenet, say, where idiotic commentary comes to haunt one forever) is sadly lacking, there is no incentive for anyone to take the time to be reasonable, logical, technically sound, ethically consistent, honest or sane.

      sigh.

      ... nous

      Toshidoshi ya Saru ni kisetaru Saru no men -- basho
    2. Re:So let me get this straight..... by rfphill · · Score: 1

      Now this is the most lucid posting I've read today. For what it's worth, you nailed it well for me...

  72. NO! He DID write vi by tnorbye · · Score: 1

    Bill Joy wrote vi.
    (And Gosling was involved with Emacs.)

    Both are at Sun.

  73. Hijacking Linux by Anonymous Coward · · Score: 0


    Of course, there is a lot of animosity between
    Sun and Apache. This is just an offshoot of
    the animosity between Sun and the open-source
    movement in general.

    Everyone seems to have forgotten the quietly
    mentioned announcement that was inserted in the
    big announcement about Sun selling Intel-powered
    servers running Linux. Namely, Sun fully intends
    to create its own distribution of Linux and to
    bypass RedHat and Suse.

    Sun fully intends to hijack Linux, which is the
    core of the open-source movement. Seize the OS.
    Then, all the applications are at your mercy.
    (This whole thing smacks of Microsoft and its
    strategy for Windows).

    Note that IBM is working fully with RedHat and
    Suse. IBM is not creating its own distribution of
    Linux.

  74. Re:Java vs Apache, its an easy decision. by donglekey · · Score: 1

    I show you when I introduce the solve_everything keyword into ANSI C++ complete with problem overloading. (Pun Intended)

  75. Re:SUN<=M$, (Sun+Oracle+Apple)>=M$ by Anonymous Coward · · Score: 0
    Sun, Oracle and Apple together destroys OSS more than M$ does:
    Sun - proprietary extensions (like logging) to their proprietary Java platform;
    Oracle - proprietary extensions (like SQLJ) to their proprietary DB;
    Apple - proprietary API, GUI in OS and propriteray extensions of PPC platform.

    all three may have chance to fix the situation by doing a better co-operation with OSS comunity.

  76. Re:Java vs Apache, its an easy decision. by Anonymous Coward · · Score: 0
    The problems with *emacs: (1) it's too selfish and not enough integrated with other applications; and (2) elisp VM is used only in *emacs though it might be potentially used even for web-services; and (3) there is no good XML support and thus *emacs is outdated from modern technologies.

    *emacs is not the only "lost" technology. Look at TCL buried in Sun, or OpenDoc/CyberDog buried in Apple.

  77. What an unsubstantiated crock by Anonymous Coward · · Score: 0

    This is all nonsense. Some dude talked to some other nameless Sun dude (off the record, of course). Show me on record where Sun is supporting J*Boss - you won't be able to find it. Sun just wants to string the open source developers along in do far as to do damage to Microsoft and when they win the mindshare of programmers they will sue whoever will prevent them from collecting J2EE licensing revenue.

  78. Re:Who cares? by knewbee · · Score: 1
    That means, simply, that data integrity, scalability, and security are top design goals for the application. And if not achieved, the product is useless for an enterprise environment.

    Its not the run of the mill, hacked it together in a week, small office application.

  79. Re:Java vs Apache, its an easy decision. by knewbee · · Score: 1

    VB "programmers" need love too! I, admittedly, am an apparant moron, by your standards. I have used VB, recently, to "program" I guess it depends on what you are trying to achieve and how fast you need to do it, the quality needed....blah, blah, blah, etc. If I have to do a windows application, and VB is a suitable alternative to C++, then I will use VB. It doesn't get in the way as much as C++ (not counting the runtime req's, and code bloat) and is a higher level language.

  80. Re:Apache/Sun (time for the lawyers) by blue+trane · · Score: 1

    ...except that apache's tomcat is not a competing product, since it is the official reference servlet/jsp implementation.

  81. Tim O'Reilly on Java by master2b · · Score: 1

    I asked Tim his opinion on this because I like his thought process on these types of issues . . . but he didn't reply . . . maybe this will get his attention :-).

    ---

    At 11:53 AM 5/17/01 -0700, you wrote:
    >Name: Siri Dhyan Singh
    >Email: my email
    >Subject: Java adoption
    >
    >Would open sourcing Java increase its adoption?
    >
    >In some of your earlier responses you refer to the lack of adoption of
    >Java by the open source community as a 'religious' issue. On the other
    >hand you also state that the control of any one standard by a single
    >business entity is subject to coercion and well meaning sentiments don't
    >necessarily survive mergers, acquisitions, or changes in management. Is
    >the Java community process enough to keep Java on track?
    >
    >Do you view enforced object orientation as furthering interoperability and
    >enhancing development efforts?

    --

    Listen to Reality!