Slashdot Mirror

← Back to Stories (view on slashdot.org)

Sun Works With Apache Software Foundation

Posted by Hemos on from the he-said-she-said dept.

The Jakarta group had raised some concerns over the proposed Java Specification Participation Agreement. After some hemming and hawing, it appears that the Java Community Process chair (Sun) has agreed with the ASF's concerns - but IANAL ? . If you have more info, paste it below.

4 of 129 comments (clear)

  1. I'm not really suprised... by thesupraman · · Score: 4, Insightful

    With Apache representing such a massive (and impressive, they are certainly a great example of success)number of internet/intranet servers out there, I'm not suprised Sun takes them seriously, they probably represent one of the strongest areas of java development currently.

    I would truly love Sun to take java *implementation* a little more seriously, they seem to put a lot of work into API designs and the legal situation of java, but don't seem that commited to providing a stable and simple to install environment for developers and users.

    The number one bug bear I have repeatedly hit with java is convincing users that it is worth the trouble to get the 'right' implementation installed on a given machine to allow the required functionality to work, and this can sometimes be hit and miss, which is a big problem.

    I would love to see Sun dedicate perhaps 6 months to working with other implementers to get java working smoothly and seemlessly on a wide range of hardware and operating systems, as it just doesn't seem to yet.

    I know that microsoft has thrown a lot of hurdles in the way of java, however it's not just windows where there seem to be problems. It is just too hard to get users to get their execution environment 'right' to use.

    I think this situation will limit java to vertical apps and server use until it is addressed, as these are the only situations where the extra time to get it working is acceptable.

    1. Re:I'm not really suprised... by rhizome · · Score: 5, Insightful

      Why do so many on Slashdot people feel compelled to write FUD about Java just because it's not GPL?

      Aside from you pulling that GPL crack out of your ass (your comment's parent didn't mention the GPL once), there seems to be plenty of room for criticism of Sun's relationship with Java and OSS. Want to install the JDK on FreeBSD? Be sure to a)install a GUI; b)install a browser that works with the various linking methods that Sun uses; c) register for a sun.com account and waste time telling Sun important things like your address; d) log in; e)Agree to the SCSL; f)download something that says "Linux" in the name (there are very few references to FreeBSD at Sun, and none in the JDK download section); g)manually download the source file; h)Agree to a license *again*; i) etc...

      Leave it to Sun to infect FreeBSD with the Microsoft-style inefficiencies that FBSD has been so good at distancing itself from. It's not about the GPL, it's about Sun and the way they treat people who aren't their cheerleaders. Being an employee of wide-line Java shop, you probably don't have occasion to relate to that.

      --
      When I was a kid, we only had one Darth.
  2. Above and beyond by axlrosen · · Score: 4, Insightful

    It really looks like Sun went above and beyond the call of duty here. I doubt Apache expected them to use $3 million of their own money to help fix this, but they did it anyway because it turned out that that was the only way to fix issue #4 on their list. Pretty cool. Chalk up one Open Source Brownie Point for Sun.

  3. Re:it's like rearranging deck chairs on the Titani by corey_lawson · · Score: 5, Insightful

    ...and you don't think that eventually Mono will have to do the same monkey tricks that Apache has to do now with Microsoft? All MS has to do is make a key piece of functionality proprietary and not disclose it to Mono, and they have many legal layers they can wrap it under, just like with Samba and Kerberos. Will ActiveState release Perl.net for non-Win32 systems? Will the (crazy?) people who put out Cobol.net do the same? Will MS allow some of the libs used by .Net to be made hostable from non-Win32 systems?