Slashdot Mirror


Java: One Step Closer To Open Source

Ritalin16 writes "Sun Microsystems on Monday intends to celebrate the 10th anniversary of its Java programming language by sharing the proprietary source code for several key Java applications used by corporate customers. Sun officials believe that by making the source codes open to developers, they will spur more involvement and use of Java-based applications."

318 comments

  1. Read the "fine" article, please by FortKnox · · Score: 4, Informative

    Ahh, someone who wants to make a front page slashdot article, but doesn't understand Java. What's worse? The editor that posts it, and doesn't understand java.

    The source code being released isn't "source code for several key Java applications," its the source to Sun's java application server (called "Platform Edition 9"). Other app servers you probably have heard of are WebSphere, WebLogic, and.... the open source JBoss! The reason Sun is open sourcing their app server is because no one uses it!

    If a company wants to run a giant professional website and has money to throw at it, they'll get WebLogic or WebSphere to run it. If they don't, they run tomcat (if no EJBs requried) or JBoss. No one uses Sun's app server cause its new and immature.

    This is not a step towards opening Java. The only relation this has to Java is the fact that it runs Java code and is written in Java. Just because sun open sourced it doesn't mean its thinking about open sourcing the Java lanugage.

    --
    Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    1. Re:Read the "fine" article, please by James_Duncan8181 · · Score: 1, Redundant
      Indeed the cynical might just see this as a way for Sun to look open without having to unlock anything important in any useful way whatsoever (yes, I think that the OpenSolaris licence was designed to exclude).

      Wake me when Sun
      a) stops changing their mind on every subject every day and
      b) actually open sources anything related to the actual language.

      *yawns*

      --
      "To any truly impartial person, it would be obvious that I am right."
    2. Re:Read the "fine" article, please by bheer · · Score: 3, Interesting

      Sun's app server is definitely not new and immature. It's based off iPlanet AS which if anything is older than Weblogic and Websphere. A better reason is that BEA (with Tuxedo) and IBM both have substantial experience selling app servers in general, and they know the enterprise software sales playbook by heart because they helped write it.

      Sun, OTOH, was and remains clueless about marketing software*. (Their latest foray, per-employee licensing for the Java Desktop System and the Java Enterprise Stack, got a good deal of buzz but it's far from being an MS- or IBM-killer yet.)

    3. Re:Read the "fine" article, please by Eric+Giguere · · Score: 5, Informative

      The reason Sun is open sourcing their app server is because no one uses it!

      Sun's application server has actually been free to use (including production deployment) for quite some time now, so this further step of releasing the source code under a friendly license isn't that big a deal. Let's face it, basic application servers are pretty much commodities these days, making it hard for anyone to compete in that space. With at least three open source app server projects on the go (this one, JBoss, Geronimo) it's certainly a crowded market. It's certainly not the big deal that misleading headline makes it sound like.

      Eric
      J2ME stuff
    4. Re:Read the "fine" article, please by DAldredge · · Score: 1

      And what is wrong with the OpenSolaris license?

    5. Re:Read the "fine" article, please by bmarklein · · Score: 3, Insightful

      "If a company wants to run a giant professional website and has money to throw at it, they'll get WebLogic or WebSphere to run it."

      Or they'll forego bloated commercial app servers and EJB and go with a lightweight open-source framework. These aren't toys - in fact the EJB 3 standard being developed now is largely based on ideas copied from these frameworks, as well as the Hibernate open-source persistence service.

    6. Re:Read the "fine" article, please by DAldredge · · Score: 5, Insightful

      The GPL isn't the only definition of Freedom or Free.

    7. Re:Read the "fine" article, please by Fishstick · · Score: 1

      >Sun's java application server (called "Platform Edition 9")

      I thought their app server was Sun ONE, which was originally iPlanet? Or is this something new that replaces that?

      If this is the one you are talking about, it isn't new or immature (it does suck ass, though).

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    8. Re:Read the "fine" article, please by Herschel+Cohen · · Score: 1

      Better title: Opening an application written in Java DOES NOT open Java!!!!!!

      Thanks saved me the time bothering with more misinformation.

    9. Re:Read the "fine" article, please by pete-classic · · Score: 2, Informative

      Actually, the FSF lists the CDDL as a Free Software license.

      -Peter

    10. Re:Read the "fine" article, please by CableModemSniper · · Score: 1

      Swing looks awesome! (on my mac...)

      --
      Why not fork?
    11. Re:Read the "fine" article, please by FortKnox · · Score: 2, Informative

      I didn't say anything against Spring, here. I use it with hibernate for my DAO layer and struts or tapestry for my presentation layer.

      Even with these technologies, though, I still see the vast majority of companies still will go with the commercial WebSphere or WebLogic, due to the support and extra features they get.

      I'm not saying thats the smart idea (I'm a Tomcat or JBoss supporter), but that's what I see...

      --
      Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!
    12. Re:Read the "fine" article, please by Anonymous Coward · · Score: 0

      used to be netscape application server before that

      http://www.iplanet.com/

      goes to Sun's software page where Sun Java System Application Server is one of the products listed.

      "Platform Edition 8.1" is the currently shipping release.

      GP was talking out his ass when he said their app server was called Platform Edition 9 and no one uses it because it is new and immature.

      iPlanet has been around long time, used to be available for free and was included in the Solaris media kit.

      googled up a thread on a 2001 giga report that has them at 3% market share:

      http://www.theserverside.com/news/thread.tss?threa d_id=3362

      "In August 1999, Giga published Comparison of Three EJB Application Server Solutions: IBM, BEA Systems and iPlanet (Sun/Netscape) We chose to include the iPlanet application server in that comparison because, at the time, we expected it to be a clear third in market share compared to IBM and BEA. So far, that has almost, but not quite, happened, due to iPlanet's entry into the market a year or more later than BEA and IBM, and we are projecting that iPlanet will take a 9 percent share of the 2000 market, considerably smaller than IBM and BEA. Still, among the vendors capable of moving closer to the IBM or BEA level of market share in 2001, iPlanet is one of the leaders, along with Sybase ....." -- The GIGA Group

    13. Re:Read the "fine" article, please by Anonymous Coward · · Score: 0

      the EJB 3 standard being developed now

      Bah. I'm going to wait until they release EJB13.

    14. Re:Read the "fine" article, please by DAldredge · · Score: 1

      Please explain why you feel that way.

    15. Re:Read the "fine" article, please by ievans · · Score: 1

      "No one uses Sun's app server cause its new and immature."

      Um, the Application Server is the base of the Java Enterprise Edition SDK, the reference implementation of the Java Enterprise Edition (nee J2EE) platform.

      After iPlanet fell apart, Sun combined the SDK team with the remaining iPlanet team to produce the Application Server/Java EE SDK. The code base has been around since the platform was invented.

      Granted, the Application Server's gone through way too many name changes (thanks, marketing!), which has probably caused this confusion. But, in a rare bout of sanity, note that J2EE is now Java EE, and J2SE is now Java Standard Edition.

    16. Re:Read the "fine" article, please by Decaff · · Score: 1

      Or they'll forego bloated commercial app servers and EJB and go with a lightweight open-source framework [spring].

      Spring does not remove the need for app servers. It helps make applications that run on app servers a lot simpler to write by removing a lot of the complexity. In fact, Spring even includes APIs to simplify the use of EJBs!

    17. Re:Read the "fine" article, please by njcoder · · Score: 1
      I don't know that it's fair to say that Sun is completely clueless about marketting software. I remember a netcraft report that said their webserver software was still the most popular among fortune 100 companies. I think their problem is marketting their software outside large enterprises. They seem to be making some progress in that, or at least are starting to make moves in that direction.

      What bother's me is that slashdot submissions like this. The article doesn't talk about open sourcing Java. The headline states they are open sourcing the app server. Seems like people intentionally post it this way to start up the old Sun isn't open sourcing Java arguments and Sun is saying one thing and doing another, when it's the submission that is wrong... not what Sun is saying.

      One thing Schwartz said was...

      "This is one step forward as we continue to open-source all of Sun's software assets," Schwartz said. "It's good for business. It's also good for the world."
    18. Re:Read the "fine" article, please by Anonymous Coward · · Score: 0

      It's the only one that matters.

    19. Re:Read the "fine" article, please by DAldredge · · Score: 1

      Why?

    20. Re:Read the "fine" article, please by Anonymous Coward · · Score: 0

      How many times in the last week have you posted about Sun? Sun vs. BSD, Sun & GPL, etc.

    21. Re:Read the "fine" article, please by Call+Me+Black+Cloud · · Score: 1

      I'm at Java One now and was at the general session where this was announced. It was made very clear by at least 2 speakers that this was only the first small step in opening up source code. I'm sure more will follow...

    22. Re:Read the "fine" article, please by Zwets · · Score: 1

      Hah! Next you'll be claiming that Mel Gibson wasn't referring to his software ideology in Braveheart.

      Oh sorry, that should be GNU/Braveheart.

      --
      One of the lessons of history is that nothing is often a good thing to do and always a clever thing to say. - Will Duran
    23. Re:Read the "fine" article, please by crazyphilman · · Score: 1

      Anyway, what's the difference? We've got Mono now, right? ;)

      --
      Farewell! It's been a fine buncha years!
    24. Re:Read the "fine" article, please by bheer · · Score: 1

      This is the sort of thing I meant when I said clueless. Rule 1 of the enterprise game: never let them doubt your commitment to your software. Even Microsoft, with its 7+5 year prouct lifecycle, has learnt this.

  2. Too late Java is not cool anymore by FriedTurkey · · Score: 5, Insightful

    This doesn't really matter to Java detractors. IT types, usually not programmers, will bring up the same old tired clichés.

    Somewhere around the year 2000 Java became uncool especially with younger programmers. I guess because it became an institution taught in high schools everywhere. Maybe programmers feel Java is rammed down their throats so they champion less established languages even something by Microsoft.

    Java really is the best thing out there for a lot of things. Sun can give away everything and detractors will be like: "OK but what about your first born child?"

    1. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 1, Insightful

      As a Java-skeptic, what strikes me is that Java can't seem to make it's mind up about what it wants to be. Is a general purpose applications language? Is it a server-side glue? Is it a VM based "Compile once, run anywhere" language?

      I was always under the impression that the last item on that list was the reason for Javas existence, yet it is the most problematic and underutilised feature-set of them all. So Java becomes some sort of over-blown (C++)++ without the maturity or standards support. I don't see the attraction.

      From a user perspective it's even worse. When you add the fact that after a decade of development, Sun still have not solved the problem of incompatible JRE's. A typical image we roll out for our users here has at least two JRE's installed. A developers image can have anything upto five, depending on which development group they're in. You have to have the exact versions installed in the right places and be in an exact order in your path, or shit just stops working. I could do without that sort of dependency juggling, frankly.

    2. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0, Interesting

      While true that Java isn't cool, I believe your reasons are wrong.

      Java requires users to install a massive runtime evironment or SDK just to run Java applications. Trying to get this setup and working is annoying at best.

      Java has fairly large overhead due to the massive runtime environment mentioned above.

      Performance-wise Java is not bad in some areas but lack of control of certain things can prevent many types of applications from even being possible in Java (if you want usable performance).

      Many of the early Java APIs were just broken and it took so long to get them fixed (due to Sun controlling everything) that many people gave up and moved on. This burned many people in the early days (myself included; on 3 very large projects back in the mid-90's).

      In a lot of areas Java is simply too object-oriented. Many of the APIs are annoying to use because of this. This is the same thing that killed SmallTalk and Objective-C. Being forced tightly into one paradigm is too limiting (future language authors take note!).

      The "safeness" of Java is an illusion that caught many people off guard. What they learned is that although it prevents a certain class of errors (memory leaks; memory smashing), if you program fails it still crashes. Bad logic is bad logic no matter how "safe" the language is.

    3. Re:Too late Java is not cool anymore by TheRealMindChild · · Score: 1, Interesting

      I will tell you why Java "Isn't Cool"... because while it may be "Write once, Run Anywhere", how the HELL do you expect an end user to run JavaApp123, when all they download is a .class file? Why in GODS NAME does Java NOT USE Native Widgets? I mean, I can spot a Java application light years away. It doesn't integrate cleanly in ANY regard. My quote "Sure, you can run it, but why would you want to?"

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    4. Re:Too late Java is not cool anymore by SparafucileMan · · Score: 0, Flamebait

      java was never "cool" except for a brief spat during the mid-90s. then people realized it was a crap language to write in.

    5. Re:Too late Java is not cool anymore by mwvdlee · · Score: 1

      Have you seen Eclipse?
      It's a pretty good IDE, outdoing atleast he ones I know including IBM's VisualAge, MS's VisualStudio and Borland's RAD IDE, and it even looks native too!
      And I'm sure there are tons of other, more recent, Java applications that look as native as any native non-Java application.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    6. Re:Too late Java is not cool anymore by afd8856 · · Score: 3, Informative

      massive runtime: last I look, the NET framework had me download about 40 megs from msft (includes sp1), while java stands at about 15 megs. The installation is a lot easier than NET (I had to run net twice because of some error, plus the service pack, which I needed for my app to work.

      And I don't find any java app to be slow.

      --
      I'll do the stupid thing first and then you shy people follow...
    7. Re:Too late Java is not cool anymore by hode · · Score: 2, Interesting
      Microsoft is rammed down the throats of student programmers in high school and college too. And unfortunately they're still around...

      I think what made Java uncool was the development of hundreds of clunky apps written in java for the cross platform benefit but left with their ugly windows interface. Think Azureus.

    8. Re:Too late Java is not cool anymore by cyngus · · Score: 3, Insightful

      Maybe Java isn't cool on the client side, but its sure is used widely on the backend. I see many, many posting each day for Java programmers, as I'm looking for a way out of this hell hole I work in. When I first started writing Java I scoffed at it, my background educationally is in systems, so C and maybe C++ are my domain. But, if you need to throw something together quickly Java is a great language, not so much for the language features, but rather the API that comes along with it. I live by "make it work, make it right, make it fast" philosophy, and you can do the first two with Java very well. With some time you can even do the last one, but half the time development deadlines don't allow me to optimize things.

    9. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      All that self promotion and no link to a resume?

    10. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Azureus for one. I couldn't believe that was a java application the first time I saw it running.

    11. Re:Too late Java is not cool anymore by Laser+Lou · · Score: 1
      Why in GODS NAME does Java NOT USE Native Widgets? I mean, I can spot a Java application light years away.

      You can run native widgets quite well using SWT. There's nothing stopping you from doing that.

      --
      No data, no cry
    12. Re:Too late Java is not cool anymore by duncanIdaho.clone() · · Score: 3, Insightful

      I mean, I can spot a Java application light years away.

      Perhaps Java's widget defaults aren't set to please everyone, but if someone releases a program that looks like ass it's their fault, not Sun's.

      --

      feints within feints, wheels within wheels

    13. Re:Too late Java is not cool anymore by TheWormThatFlies · · Score: 1

      This is "+4 interesting"?

      "Oh well, all those mean, stupid people who disagree with my point of view for no rational reason are going to disagree with it again. I bet they are going to make specious arguments A, B and C. Obviously, the reason they all hate the thing I like so much is petty justification X, and they won't be swayed by any reasonable arguments. Which is a pity, because the thing I like is the best thing ever, and totally unfairly maligned and oppressed, as you can clearly see."

      If this isn't trolling, it's certainly fishing for a reaction.

      What does it even have to do with TFA? Mind you, it doesn't help that the headline, which is supposed to give some vague indication of what TFA is about, has nothing to do with TFA either.

    14. Re:Too late Java is not cool anymore by Tony+Hoyle · · Score: 1

      The last place I was at abandoned java (at considerable cost.. 6 month rewrite) because Sun couldn't release a JRE that didn't have major bugs in it.. there seemed to be no quality control - things would be fixed in one release and break again in the next one (the proxy server bug was supposed to be fixed in JDK 1.3 but *still* wasn't fixed in JDK 1.4, except for one specific version where they actually fixed it - then broke it again in the next release.. We had to stick with JDK 1.2 long after it was obsolete because corporate customers often use proxies).

      Also JDK 1.2 wasn't compatible with JDK 1.3 which wasn't compatible with JDK 1.4.. if a customer had a java app on their system that was a different java version, they couldn't run our software - so much for 'run anywhere'!.

    15. Re:Too late Java is not cool anymore by LWATCDR · · Score: 1

      Since when is cool important for programmers?
      Java is used a lot to write internal apps. It is a MUCH better choice than say... VB.
      As to it not looking right? I don't know about that. My java applications look very much like native applications. They are not slow except at start up but since people fire them up at the beginning of their day and run them until they leave that is not a big issue.
      Of course I have heard valid complaints about java missing the templates of c++ and other features but when someone says.. Java is crap I can almost bet that they have have never written line one of code.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    16. Re:Too late Java is not cool anymore by Cthefuture · · Score: 1

      SWT provides a decent native widget toolkit. That is what Eclipse uses. However, any GUI done in Java always has a funky clunky feel (even when using SWT). Just play around with Eclipse and you'll see. Although surely some Java zealots will come to flame me, they are looking through rose colored glasses because the fact remains that Java GUI apps just don't feel as snappy as the alternatives.

      Also, the "Write once, run anywhere" thing never panned out. Both because you need to install that huge JRE (no matter your platform) and because all you need are cross-platform libraries and any language is just as portable as Java (often even more portable). The usefulness of only compiling once for all platforms is miniscule.

      --
      The ratio of people to cake is too big
    17. Re:Too late Java is not cool anymore by fimbulvetr · · Score: 1, Insightful

      P.S.: You're obviously bullshitting if you say "I don't find any java app to be slow".

      Either that you've never installed Oracle, or used Suns Patch management tools, or used the java solaris installer, or used eclipse...or any number of other applications...

    18. Re:Too late Java is not cool anymore by Decaff · · Score: 5, Informative

      how the HELL do you expect an end user to run JavaApp123, when all they download is a .class file?

      Users almost never download class files. They download JAR files. JAR files can have a Main-Class property which means that with a JRE installed the user need only double-click the JAR to run it.

      Why in GODS NAME does Java NOT USE Native Widgets?

      Because native widgets can a wide range of capabilities on different platforms. The Java widgets are usually a superset of these capabilities, allowing a rich interface to be cross-platform.

      I mean, I can spot a Java application light years away.

      That is the developer's fault, not Java's. Java ships with the option to use widgets that have a very close match to the native OS widgets on platforms such as XP and MacOS/X (on the latter, they are indistinguishable). Sun is working to ensure that Java apps are completely visually compatible with Windows apps on the next version of Windows.

      It doesn't integrate cleanly in ANY regard.

      Yes it does. There is an API called JDIC (Java Desktop Integration Components) that allows very good integration with the GUI of a system, from using the 'systray' to opening native browsers and so on.

    19. Re:Too late Java is not cool anymore by poot_rootbeer · · Score: 2, Informative

      how the HELL do you expect an end user to run JavaApp123, when all they download is a .class file?

      You could use WebStart, so that the user downloads a .jnlp file, which then automatically downloads the latest versions of all necessary .class and other files. It's pretty painless.

      Why in GODS NAME does Java NOT USE Native Widgets?

      One good reason is that many native widgets do not behave equally on different platforms. But that's beside the point, as there are plenty of desktop Java apps that DO use native widgets. Azureus and Eclipse, for two...

      My quote "Sure, you can run it, but why would you want to?"

      Because one luser bitching about the scroll buttons being the wrong shade of grey is less important than saving the developers from having to rewrite the screen management code from scratch multiple times for each target platform.

    20. Re:Too late Java is not cool anymore by afd8856 · · Score: 2, Informative

      Of what you've listed, I've used only eclipse. Really, I don't find it slow for what it does compared to any other complex application. Have you looked at dreamweaver, ilustrator, or any other modern complex application and see how slow they are? And there's no java to blame there. Being slow is a consequence of today's complexity and modern development techniques, you simply can't say "Java" and expect it to mean "slow".

      For simple apps to medium apps, java is not slow. I can mention here azureus, sanchez, jedit, hot potato, freemind, some custom apps that I have met in my work, etc.

      --
      I'll do the stupid thing first and then you shy people follow...
    21. Re:Too late Java is not cool anymore by LittLe3Lue · · Score: 2, Informative

      Oracle, Slow?

      Are you mad?

      Sure, the instalation software is crap, but I dont think you can blame java directly.
      If I wasn't at work I would do a little googling around for performance comparisons.
      For reasons like your statement above I did some research a year ago as I was doing some java development to see just how slow java was, and, yes, the first many releases of java were quite slow, but the latest version are not.

      Sure, its not as speedy as a C program, but its not designed to be. Ill take the developement cycle and portability ease in most situation that dont require absolute speed.

      I have done solar simulations in java with advanced mathematics and OpenGL and they have been very speedy. Just need to do it proper.

      Bah.
      Here.
      This is just one of many articles actually comparing performace: Take a look at the benchmarks, SciMark 2.0 (in Java, C# and C) being the easiest to deduce results.

      Clearly Java is faster than even C in some cases, and almost always faster than C#. Momo doesnt even compare, so portability is very inefficient.

      Java is awsome, for the right purposes. Dont bash it.

    22. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Mod this one down please! Uninformed flamebait!

    23. Re:Too late Java is not cool anymore by mattcasters · · Score: 1

      Perhaps it has something to do with the fact that
      - Oracle UI has to install 1Gb+ of data
      - Eclipse is a very complex application
      - ...

      and less with java?

      I write software using SWT and the speed (after loading) is not different from a native application.
      (webstart: http://kettle.ixor.be/spoon.jnlp)

      That doesn't prevent anyone from writing a bad application though. From *my* sysadmin days I can remember PLENTY of applications that were slow to the point of almost being unusable that had nothing to do with java.

      Peace,

      Matt

      --
      News about the Kettle Open Source project: on my blog
    24. Re:Too late Java is not cool anymore by Taladar · · Score: 1

      Why is Eclipse always cited when someone says either "Java looks like crap", "Java is slow",...?

      Might it fit into your head that Eclipse (and Azureus which would probably be cited when I wouldn't mention it here) is the only decent (as in: not slow, doesn't look like crap) Java Application out there?

    25. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Wow! How effective!

      1) Post Anonymously
      2)Give zero feedback as to your post
      3)...
      4) Profit!

      Or something like that. Retard. Just remember... if you aren't part of the solution, you are part of the problem

    26. Re:Too late Java is not cool anymore by lurch84 · · Score: 0

      Why in GODS NAME does Java NOT USE Native Widgets? Ever played with Java-Gnome? True, some aspects are still under development but you can make some pretty good looking gnome apps with it.

    27. Re:Too late Java is not cool anymore by -brazil- · · Score: 1

      Well, my experiences have been quite the opposite. Between two big commercial Java apps I've worked on, I've personally seen a whopping TWO JRE-version related problems. In one instance someone was using some weird beta JRE that was missing a mandatory encoding. In the other, the app was operating the the legal gray zones of focus management and working on the old JRE more or less by accident.

      Seems to me that if your app had that many problems between different JREs then you were doing something wrong.

      --

      The illegal we do immediately. The unconstitutional takes a little longer.
      --Henry Kissinger

    28. Re:Too late Java is not cool anymore by Taladar · · Score: 1

      I can see from your post that your knowledge about programming language features is very limited. Otherwise you might actually start to miss lots of the better ones in Java. For an Overview see the Wiki at c2.com (Portland Pattern Repository)

    29. Re:Too late Java is not cool anymore by iced_773 · · Score: 1

      While I like Java's class hierarchy, I have two complaints about the language itself:
      1. No pointers. Many times when writing in Java I have figured that a pointer would work well, but instead I have to write a zillion lines of code to work around it. This can lead to slower programs, and ones that may not run at all on older machines.
      2. JRE. Every machine that runs Java software must have the JRE installed, which can be a pain if you are writing commercial software. I know Sun loves to promote its "write once, run everywhere" ideology, but if you are writing mainly for one platform (in my case Windows), couldn't the JDK have an option to compile the bytecode into binary for that platform?
      These two things tempt me to switch to C#. Yes, it's Microsoft, but at least it supports pointers and compiles into executables. AFAIK, the .NET Framework is a similar class hierarchy and if you have been running Windows Update like you should, .NET applications should run properly.

      Will the JRE be coming through WU? I don't think so. I know it can't be helped, but when developing for Windows, I'd rather write for a framework that is already there.

    30. Re:Too late Java is not cool anymore by dnoyeb · · Score: 2, Informative

      "Sure, its not as speedy as a C program,"

      Actually, it _is_ a C program. Only the GUI was ever slow, and that was over 10 years ago. Anyone that calls Java slow today is either ignorant or trolling.

      I use Eclipse and its not slow either. Its funny to even call Eclipse slow as it uses native widgets for even faster (but mainly more native looking) operation.

      I think he was just a troll.

    31. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Java-gnome is horribly broken and half-finished. The bindings are full of inconsistencies and large, important, chunks of API are unbound; serious bugs go unfixed and the developers live in a "make it more Java-ish lah-lah land" while hand-writing bindings for versions of GTK that won't be in general use until 2006, at least.

      I know Red Hat are pushing Java (and include Java-gnome in FC4)... but if they want Java to be used for GNOME apps, they are going to have to do a hell of a lot better than Java-gnome.

    32. Re:Too late Java is not cool anymore by LWATCDR · · Score: 1

      I never said that Java was perfect. The only perfect programing language is lisp. Just ask any Lisp programmer.

      I have on thing that drives me crazy about C++ and that is there is no base object. That and MFC but that is not a flaw with c++ as much a flaw with c++ Windows programmers. USE THE STL AND BOOST FOR GOODNESS SAKE!

      My main statement is that for many small and not so small applications java is a good tool. I have used it for a few internal apps and those apps work great. I could have written them in C++ but I also wanted them to run under Linux as well as Windows.
      I question the opinion that of those that just state "it sucks". I looked at your link and it is vast. I will have to spend some time looking at it.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    33. Re:Too late Java is not cool anymore by leonmergen · · Score: 1

      Exactly, just like OOo and Azereus... they all pretty cleanly integrate into the OS, and users don't seem to have much problems installing it - so what's all the fuzz about ? You just need to make sure you have a good installer application, but hey, you should have that as a requirement anyway...

      --
      - Leon Mergen
      http://www.solatis.com
    34. Re:Too late Java is not cool anymore by Decaff · · Score: 4, Insightful

      Oh hahahaha... yes, if your app doesn't look completely native it's the developers fault. Fuck me, I have to wonder what planet you live on.

      This one. Your average user won't notice much difference between Swing and native on Windows, and will not see any difference at all on MacOS/X.

      Speaking as someone who has tried Swing under Linux and Windows, I have come to the following conclusions... and this is based on actual usage, not theoretical bullshit and Sun marketing (like your reply):

      Actually, I am a Java developer, who has had substantial practical experience of it since it started. It has been my main development language for about 5 years.

      1. Swing sucks balls under Linux. It's very very slow (and believe me, looking slow compared to GTK is quite an achievement) and ugly... even with the gtk plaf it stands out like a builder wearing a pink tutu to work.

      Swing works fine under Linux. It is fast and very user-friendly (I find novice users have no problems with it at all).

      2. Swing sucks balls under Windows... even though Sun have put a huge amount of effort into speeding it up by using all kinds of directX acceleration to hide just how slow it is.

      On the contrary, Swing is pretty good under Windows. It has good desktop integration and is very fast. The DirectX application means it is at least as fast as native apps.

      3. Sun's entire Java package for Linux sucks... and it's only going to get worse. Sun's Linux support is grudging and half-assed at best.

      Sun's package for Linux is first-rate. Not only have they directly supported it for years, they now ship Linux with Java installed as a product.

      Why do you think so many people hate Java on slashdot? It's partly a license thing... and partly that Java is a corporate quagmire and on Linux it is seriously shite.

      On the contrary, its a combination 'not invented here', geek culture not liking 'safe' languages where you can't hack everything and a dislike of everything that isn't open source.

      Linux is one of the main deployment platforms for server-side Java, and Java is very widelyused this way for high-performance critical applications.

      So I am afraid the evidence is strongly against your 'seriously shite' claim!

      The fact that you can claim Java is in *any* way a serious system for cross-platform desktop development betrays a complete and total break with reality. You might try using it in the real world.

      I do, and have for years. It's cross-platform ability is superb. I have written substantial (hundreds of thousands of lines) Swing and Web applications and these have ported between Windows and Linux with no changes.

    35. Re:Too late Java is not cool anymore by dnoyeb · · Score: 2, Insightful

      Then you missed the point. The JVM itself optimizes for you. I still fail to understand how people think they can write faster code in less time in c/c++ when java itself is just another c/c++ program that is handling many other tasks for you.

      If you would say in the long run you can manually optimize a c/c++ program to give you more speed, then I would say ok. But for me, I have a team of engineers working to make my program faster for me. They are called JVM developers.

      Java is simply a c/c++ program that does a lot of things for you and is written and maintained by someone else.

    36. Re:Too late Java is not cool anymore by Laser+Lou · · Score: 1

      Its clear that you don't highly regard swing, but have you looked at SWT? It might change your opinion of Java. It enables a truly native GUIs for Java programs. Take a look at the Eclipse IDE for an example.

      --
      No data, no cry
    37. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Who said anything about .NET? Did I say it was any better? Although from a pure language standpoint I like C# better than Java. I don't use C# or Java for most projects though.

      I never said Java was slow. It's just slow for certain things. The reason you don't see any slow Java apps is because many people have moved on (or back to) to better languages. So you only see the limited set of applications that are possible in Java because those are the only ones that work well in Java.

    38. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      COBOL is a crap language to write in. However, it's used all over the place - (literally) billions of lines of it. Being a crap language has no impact on how popular it becomes.

    39. Re:Too late Java is not cool anymore by fimbulvetr · · Score: 1

      I didn't mean that to imply that oracle was slow, just the installation. Of course, Oracle has it's moments, but that's neither here nor there.

      I was merely calling BS on the guy who said he's never seen a slow java app.

    40. Re:Too late Java is not cool anymore by suitepotato · · Score: 1

      As a Java-skeptic, what strikes me is that Java can't seem to make it's mind up about what it wants to be. Is a general purpose applications language? Is it a server-side glue? Is it a VM based "Compile once, run anywhere" language?

      Is it a topping? Is it a floor wax? No, it's both.

      The question for end users is, "when the fark will people implementing Java speed it up?!" Java takes forever to start and do anything whether Windows or Linux. Any complex Java programs and my systems crawl.

      When they fix the speed and efficiency issues, then it will be deserving of further usage. Until then...

      --
      If my grammar and spelling are off, I am [distracted/tired/careless] (take your pick)
    41. Re:Too late Java is not cool anymore by tomstdenis · · Score: 1

      GET OUT OF WINDOWS.

      Seriously, you think the only contender against a Java applet is C++ with MFC?

      How about C with GTK+? GTK+ is not only portable but works with minimal overhead and is easy to develop for with the DRAG AND DROP gui designer Glade.

      I mean you literally drag and drop buttons, controls, whatever onto a dialog, hit "save source" and it emits C code that uses GTK+ to make the dialog.

      If you write a modular program e.g.

      backend frontend GTK+ code

      You're additions to the code that Glade produces are minimal and the entire design process is portable any number of other platforms [e.g. other Linux, BSD, MacOS and even windows OSes]. ...

      Once you pull your head out of your arse and try new tools [e.g. non-mandated by the three week devry college you went to] you'll learn there is a "whole big world out there" of other tools and development methodologies.

      Tom

      --
      Someday, I'll have a real sig.
    42. Re:Too late Java is not cool anymore by vrai · · Score: 1

      Good point, except that the JVM developers have continually proven themselves to be less than stellar. If I have to rely on someone elses code to that extent I expect it to be written by people at least as good as me or my colleagues. I've seen nothing from the Java platform that suggests that's the case.

    43. Re:Too late Java is not cool anymore by chris_mahan · · Score: 2, Funny

      I would like to add jedit to that.

      Yes, it is slow at times, but it's a text editor, and I type even slower.

      --

      "Piter, too, is dead."

    44. Re:Too late Java is not cool anymore by alucinor · · Score: 1

      Sun will never open source Java because they're too afraid that the Eclipse foundation will essentially fork it out of Sun's grasp into the hands of the open source community. This is an inevitability, but Sun's desire to hold on to Java, while possibly giving the company some credit with a few groups, ruins their image with most, and smothers Java into irrelevancy as the open source scripting languages (PHP, Python, Ruby) mature into enterprise use.

      Eventually, Java will become open source once Sun is bought, probably either by IBM or RedHat. Then and only then, Java may get up to speed with the rapid pace of 21st century software development.

      All the same, Java will just be a dialect of the open infrastructures of the future, where choice of programming language for web development will undoubtedly make little difference.

      --
      random underscore blankspace at ya know hoo dot comedy.
    45. Re:Too late Java is not cool anymore by jjshoe · · Score: 1

      apparently you've never played with swing's native look and feel options.

      from your post i'm guessing you've never even seen source code for java. (java != javascript)

      --
      -- botsex is {grep;touch;strip;unzip;head;mount} /dev/girl -t {wet;fsck;fsck;yes;yes;yes;umount} {/de
    46. Re:Too late Java is not cool anymore by N1KO · · Score: 1

      "In theory, communism works. In theory."

      In theory, java programs are as fast as native ones. In theory.

    47. Re:Too late Java is not cool anymore by fimbulvetr · · Score: 1

      On the oracle statement:

      Sure, oracle does have at least a gig of stuff to install, but that's a poor excuse, imnsho. I'm talking about the responsiveness of the installer, not how long it takes to get from 1% to 99% complete. Like when you hit next and it takes 10 seconds for the box to redraw itself (running locally). Like when you close it, and it doesn't actually close until you kill -9 it. Like how when you leave it open before you go to lunch and you get back in an hour and it's eaten all of your memory. Like how long it takes for it to just start up!
      Sure, these are just anecdotal, but I still think someone needed to call BS to the grandparent who claimed to have never encountered a slow java app.

    48. Re:Too late Java is not cool anymore by LWATCDR · · Score: 1

      You are a nasty little fellow aren't you?
      GTK+ is fine for things like GUI but not for things like database access. Java is a more complete cross platform solution.
      Guess what buddy. I did not write the MFC code. I was called on to help make it more portable. Even parts of the code that where not GUI where full of CStrings and a bunch of other crap. That is is why I said for goodness sakes use Boost and STL. Maybe you have not heard of them. Frankly I am suggesting we go to QT for the cross platform library.
      As far as heads up an arse...
      Let me explain one thing about programing in the REAL WORLD. I.E. Where you get a paycheck for doing it. Often you do not get to choose what library and or toolkit to use. If other people may have to help on the project or support it after you are gone you have to pick a library that everyone knows. Also as little as a year or two ago GTK+ was not all that stable under Windows.
      From the CURRENT GTK+ page on Gimp.org
      http://www.gimp.org/~tml/gimp/win32/

      Warnings
      Program(s) that use these libraries might crash unexpectedly or behave otherwise strangely. (But of course, so does much software on Windows.) The stability seems to depend a lot on the machine, display drivers, other software installed, and whatnot. Using NT-based Windows versions (Windows 2000 or better) is very much recommended.


      Hummm since I have had no stability problems with java and at least one of them is mission critical and has not had any downtime for 3+ years. WHY is GTK+ a better solution?

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    49. Re:Too late Java is not cool anymore by TheRaven64 · · Score: 2, Insightful
      Why in GODS NAME does Java NOT USE Native Widgets?

      Because Java apps are not native apps. If they look like native apps then you have lost the visual clue that they are not native apps. The correct way to implement a Java app is:

      1. Write the core logic and a Swing GUI, which will run everywhere.
      2. Test everywhere.
      3. Fix bugs.
      4. Hand over to UI specialists who will write platform specific front ends using things like the Java/Cocoa bridge on OS X or the GNOME Java bindings.
      5. Test and fix bugs again.
      Just because you can run your code on a platform doesn't mean it's a native application on that platform. Cross platform toolkits are a good for first approximations of a native port, but they should never be treated as if they are actually native.
      --
      I am TheRaven on Soylent News
    50. Re:Too late Java is not cool anymore by The_Dougster · · Score: 2, Informative
      Sure, its not as speedy as a C program, but its not designed to be. Ill take the developement cycle and portability ease in most situation that dont require absolute speed.

      That's a pretty good summation of how I feel about it. I use Python if I really don't care about the execution speed and want the quickest development times. Java is a step up the rung and its much more suitable for use in business environments.

      Python is great for a quick and dirty implementation, and C++ is good if you are making a commercial product, but if your app is going to be used by your average corporate shmuck for an in-house system then Java is a smart choice. Java based database frontends are easy to maintain, robust, and very professional looking, and this is where Java shines most brightly I think.

      --
      Clickety Click ...
    51. Re:Too late Java is not cool anymore by tomstdenis · · Score: 1

      Speak for yourself. I'm not working some two-bit gui-pumper shop. I'm doing R&D and I can use pretty much anything at hand to get the job done.

      Where we have a standard for OS/tools are on the hardware boxes and that's just to make the debuging process simpler.

      As for Java vs. GTK+ that's not the point. I was trying to point out that "if you're not using Java there is more than C++ with MFC to use." You go from one extreme to the other.

      Might as well say "I would switch from Java but COBOL is just so old!" or "I would switch from breathing but hot fire pokers in the eye just hurt to much!"

      Tom

      --
      Someday, I'll have a real sig.
    52. Re:Too late Java is not cool anymore by tolkienfan · · Score: 1
      It'd be nice if you'd acutally give some examples.

      Are you refering to language features? Maybe there's some syntax that you're fond of which Java doesn't support?

      Since you don't give any details, it's kind of hard to guess.

      If it's library features, you'd be hard pushed to find a wider selection of libraries anywhere.
      Maybe the C++ STL, but that's rather limited in scope... 99% of apps don't require anything in the STL, even though the STL would probably help 99% of apps.

      Perhaps it's the language itself? You want operator overriding? It's desperately important to your project?

      Or native compiling? ('course you could try gcj)
      Maybe you want different kinds of heaps, or more control over object destruction?
      In those cases, you're out of luck, because they are against the basic direction of Java.

      Nice diatribe, but fairly empty of content.

    53. Re:Too late Java is not cool anymore by m50d · · Score: 1
      Sun can give away everything and detractors will be like: "OK but what about your first born child?"

      No, sun can try giving away anything else it likes for publicity, and I'll be like "Thanks, but all I care about is Java". Props for opening Solaris, that is something that matters, but what the hell is the point of opening up Java3D (for example) when the base java is not open?

      --
      I am trolling
    54. Re:Too late Java is not cool anymore by tolkienfan · · Score: 1
      Hardly matters, since .NET will be part of the Windows OS...

      Shame Java can't be preloaded with Linux distro's!

      I mean - imagine if there were a 100% platform independent API that you could write against that was avaible on most platforms - already integrated with the environment.
      And without the minor differences you find in *nixes, resulting in all the config.h and autoconf messes.

      And from GP:
      Performance wise, Java suffers from large start-up time, since the JVM has to start. It also suffers from a large memory footprint - constraints here cause more GC than would otherwise be the case, resulting in higher latency. This is bad for GUIs, but less important for server contexts.
      Other problem areas result from the lack of destructors. Many programming techniques result in objects to be created for very short term use. Plus some objects have outside resources - like GUI widgets or connections. These resources can be held onto until GC - way beyond the time the object would have been freed in, say, C++.

      These things can be programmed around (apart from JVM startup time), but it does mean that it is easier to write faster code in some other languages.

    55. Re:Too late Java is not cool anymore by tolkienfan · · Score: 2, Interesting
      You need to give examples of where the Java API isn't backware compatible.

      There are some documented areas, but I haven't run into any instances that weren't documented.

      I think Sun has had an exemplary record in backwards compatability, especially when compared to other platform vendors, and when you consider that Java runs on so many OSes.

      My biggest gripe about Sun with regard to Java is in the JDBC specification.
      For example - Can a Connection be used by more than one Thread?
      Anwser: It's not detailed in the specification - it's vendor dependant.
      This is a bad thing to do in a specification - it means that as a coder you can't rely on one kind of behavior. Or you have to limit to one vendor.

      Perhaps you're refering to non Java-platform APIs, like those in the sun. packages?

    56. Re:Too late Java is not cool anymore by LWATCDR · · Score: 1

      "As for Java vs. GTK+ that's not the point. I was trying to point out that "if you're not using Java there is more than C++ with MFC to use." You go from one extreme to the other."

      I never said the choice was Java or C++ and MFC. What I said that MFC sucks and that Windows programmers should not use it. MFC or java? Not really a choice. MFC is Windows only and to be honest pretty nasty. I chose Java since I wanted it to be multi platform and three years ago there was no good multi platform solution but Java. I have not done much with the latest QT but I have hopes that it will be a good multi platform solution.
      What it comes down to is what is the BEST tool for the job. I had to replace a POS written in Delphi that used an XBase back end quickly. The program was being used to track all of our support calls. I assigned the project to myself because I was sick of the support and clerical staff having to reboot every one of there machines two or three times a day. Yes that POS would take out EVERY SYSTEM that it was running on at the same time twice a day.
      With limited experience in Java I wrote an application in a week using Postgresql as the back end. I put it up on the Friday after Thanksgiving for a test and they would not let me take it back down.
      Let me try and make it clear
      Java is strengths are
      Multi platform gui programs
      Database access
      Easy multi-threading
      error handling.
      C++ is great when
      You can not afford the memory footprint of Java.
      Speed is the most important thing.
      Access to machine specific features.

      It does not have to be one or the other. I am currently using C++ for a project because Java is not suited for it. For the Gui I am using Nano-X and FLTK.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    57. Re:Too late Java is not cool anymore by czei · · Score: 1

      The whole attitude that somehow open source is wanting more from Sun than it would contribute back is ignorant, uninformed, short sighted, etc. Sun and their apologists should get a clue. Open source would make it responsive to a much wider range of developers and would produce developments Sun was too blind to pursue or pursued way too late and too little. Any harm has already been done to a great extent by Sun's pig-headedness. They should go off in a corner and use it by themselves if they don't want to open it up.

      This is yet another post that confuses source code with a specification. Java is a programming language, and having access to the source code doesn't help if you can't also change the specification. Fortunately anyone who actually wanted to change the java language can participate in the Java Community Process.

      Making Java the language "open" so that anyone could define what the language meant would kill Java. One of the main reasons people can use Java is that it mostly runs without problems on a bunch of different platforms and JVMs. If anyone could create different language constructs and publish a new version of the java language or JVM, the new versions almost certainly would not be cross-platform, and most likely would make it so unreliable as to be unusable in mission critical applications.

      If you'd like to point out another corporation doing a better job with their programming language, go right ahead. Name one.

    58. Re:Too late Java is not cool anymore by bladesjester · · Score: 1

      If memory serves, there *is* a way to compile java into a native windows binary. I'd have to look to find it again, but i do believe it's there.

      --
      Everything I need to know I learned by killing smart people and eating their brains.
    59. Re:Too late Java is not cool anymore by rpdillon · · Score: 1

      Meh.

      This is sometimes an issue, sometimes not.

      I just got out of the opening session for JavaOne here in San Francisco.

      They annouced the open sourcing, but also went into features for the next version of Java (Mustang, or Java SE 6).

      One of the big ones that folks applauded was that Mustang will have native widget support on Day 1 for Longhorn. Anyway, they know about the "look and feel" issues and obviously have plans for it. It is a lot like the performance gripes people have about Java: sure, it used to be a big issue, but honestly, Sun works to improve things pretty diligently.

      That said, someone needs to teach Sun what the "Free" in Free Open Source Software means. They did a whole speech about how it's important that their software remain cost free. No notion whatsoever of Free speech. Oh well...

    60. Re:Too late Java is not cool anymore by kotj.mf · · Score: 0
      A-f'n-men.

      Our main app currently requires a specific sub-version of 1.4.

      It won't work with 1.5. We constantly have to explain this to our customers, who then need to get their own corporate IT involved, all to get the correct JRE installed on a half-dozen user's machines.

      Rather than deal with the headache of upgrading and the possibility that we'll have to do this again for 1.6, we're porting everything over to JavaScript and CSS. Because it's easier to write cross-'platform' code that way. Who'd a thunk?

      --
      hang brain.
    61. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      If you would say in the long run you can manually optimize a c/c++ program to give you more speed, then I would say ok. But for me, I have a team of engineers working to make my program faster for me. They are called JVM developers.

      However many teams of expert mechanics you have working on your tractor, it will never be faster than a sports car. (It might well have other advantages, like being better at pulling heavy loads. It just won't be faster.)

      Face the facts, dnoyeb: Java is slower than C++, for the simple reason that interpretation of bytecode is a huge overhead, even with a JIT recompiler. Java development is faster and safer than C++, but the products so developed run slower. This is a fact. It is true. It is, in most cases, completely irrelevant, because in most cases a serious programmer is more interested in robustness and ease of maintenance than in raw speed, provided performance is "good enough". But it is still true.

    62. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0
      Nnh...you probably just don't understand the arguments against Java.

      There are several problems:

      • "Write-once, run anywhere" - sadly, the portability of most of the Java runtimes (Sun/Blackdown/IBM) compatible with actual software is less than the portability of other languages which compile to native.
      • "Safer than C++" - in terms of automatic memory management, yes, but otherwise...mostly no. Until recently, Java was limited to subclass polymorphism, which made collection classes problematic ("safe", but requiring type narrowing casts that could cause runtime errors). Even C++ is safer with STL (despite how horrible STL is otherwise)


      In general, Java is far less expressive (far more verbose) than other comparable languages. Worse yet, compared to languages with things like parametric polymorphism, decent type systems (variant types etc.), multi-methods etc.

      Java generally made the "worst of all worlds" choices; nobody cared because all they knew was C or limited subsets of C++.
    63. Re:Too late Java is not cool anymore by killjoe · · Score: 1

      Too late. Java has already been forked by MS and now it's called C#. Furthermore languages like python and ruby are already nipping at the heels of java as more and more programmers want a simpler way to code their applications. Java salwarts like Bruce Eckels have written much more eloquently on this then I can but there is no doubt people are migrating away from java in droves as java gets more and more complicated.

      --
      evil is as evil does
    64. Re:Too late Java is not cool anymore by LittLe3Lue · · Score: 1

      On the one hand I agree with that Oracle Installer being one of the worst, ugliest commertial peices of software I have ever seen, but on the other I know you are overdoing the effects (or installing on a 486).

      Either way, Oracle is to blame not Java.
      Just look at the UI feal, it is clearly not standard, mainstream stuff. I dont know what they were thinking.
      Makes me wonder about Oracle sometimes.. Too bad I love it so.

    65. Re:Too late Java is not cool anymore by njcoder · · Score: 1
      When I do web development I use a number of different applications. An image editor, ide, text editor, data modelling tool, html editor, database admin tool, etc. Only one of them is a java app (the IDE NetBeans) and ALL of them look completely different. Different tabs, different menu item layouts, different dialog box formats and positions, different Open and Save dialog boxes, different toolbar button behavior, different right click behavior, different short cut key behavior (I think some other apps still don't use ctr-c ctrl-v for cut and paste), etc.

      The one that is a java application works and looks more native than some of the other applications and it's completely in Java, not SWT. It takes up a lot of memory and it's slow compared to the text editor but not slow compared to a similarly functional IDE.

      Years ago, it used to be that I would have to shutdown and restart the IDE regularly because the memory just grew too much. That's changed a lot with the performance enhancements in Swing and better designed applications. I wind up shutting down and restarting FireFox multiple times a day because the virtual memory just grows and grows and grows even after I shut down all but one window and tab. I just shut it down now because VM uusage was around 300Megs and real memory close to 200Megs. NetBeans can gets to around that memory usage when I've been doing GUI editing using the GUI tool, have the built in tomcat instance running, etc. The html editor easily eats up memory too and all it's doing is designing web pages.

      Stop picking on Java. It's not any/much worse than other apps. Where it does have performance problems is in start up time but this looks like it will be addressed in later JVM's. Also, Swing is designed to be single threaded so you'll have to specifically create you're own threads when you need to. There are sites with a lot of good information out there on how to write more performant Swing apps. It's a pain that it's not easier but with some things you can't expect the platform to know how to optimized threads.

    66. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 1, Insightful

      Sounds like your app is poorly written:

      It depends on a certain sub-version of 1.4
      Very bad. Bad bad bad bad. There is no reason to do this, other than bad.

      we're porting everything over to javascript and CSS
      If your app can be done in javascript and css, it doesn't even sound like an app. Maybe you should submit it for worst-app-of-the-year!

    67. Re:Too late Java is not cool anymore by njcoder · · Score: 2, Insightful
      " Then you missed the point. The JVM itself optimizes for you. I still fail to understand how people think they can write faster code in less time in c/c++ when java itself is just another c/c++ program that is handling many other tasks for you."

      I'm not going to disagree with you that the JIT compiler provides a lot of useful optimizations during runtime and is a great thing.... but it's not the be all end all of performance.

      I think the original poster was talking more along the lines of more design issues where profiling an application can help out. The JIT compiler may see you're making 1000 calls to the same method and is able to inline it, but it can't let you know you only really need to make that call once.

    68. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Very bad. Bad bad bad bad. There is no reason to do this, other than bad.

      Could you pop 'round Oracle on your way home and tell them about this, then? 'cos they're one of the worst fucking offenders for this sort of stupid shit.

    69. Re:Too late Java is not cool anymore by Decaff · · Score: 1

      Face the facts, dnoyeb: Java is slower than C++, for the simple reason that interpretation of bytecode is a huge overhead, even with a JIT recompiler. Java development is faster and safer than C++, but the products so developed run slower. This is a fact. It is true.

      It is not a fact. It is false. Modern Java VMs do a LOT more than just JIT recompiling. They profile the code and produce very optimised machine code for the specific processor. This run-time optimisation can potentially produce better machine code than the ahead-of-time optimising used by C++ compilers, as it is based on actual performance, not predicted. Because the VMs only optimise slow areas of code they can do this very aggressively, with inlining, loop unrolling etc. This optimisation process is getting better, and there is no reason why Java should not overtake C++ speed in future.

    70. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Well thank you Rain Man. Now go tell Oracle that they're a bad company, a very bad company.

    71. Re:Too late Java is not cool anymore by jhantin · · Score: 1
      Java requires users to install a massive runtime evironment or SDK just to run Java applications. Trying to get this setup and working is annoying at best.
      I can't argue much with that one. The standard library ballooned beyond belief and nearly beyond recognition in release 5. Sun's extension libraries (Activation Framework, Advanced Imaging, 3D, etc) are an even bigger pain in the installer because of restrictive licensing.
      In a lot of areas Java is simply too object-oriented. Many of the APIs are annoying to use because of this.
      I disagree. In a lot of areas Java suffers from excessively concrete standard libraries, stranding it uncomfortably between procedural and OO, and between process-based and capability-based authorization.

      java.io.File, java.io.RandomAccessFile, RandomAccessFile, java.net.Socket, java.awt.Toolkit, and even java.lang.System all should have been pure interfaces; any functionality that can observe or touch the real world should not be available as a static member or concrete class. Pass an instance of System as an argument to main() from which I/O may then spring: what the capabilities crowd call the powerbox pattern.

      The "safeness" of Java is an illusion that caught many people off guard. What they learned is that although it prevents a certain class of errors (memory leaks; memory smashing)...
      Memory smash bugs tend to translate into gaping security holes, and they are regularly and frequently being found in all kinds of network-facing code. I, for one, welcome our new memory-smashless language overlords. ;-)

      As for memory leaks, when a garbage-collected program leaks memory it's typically due to references being kept alive that shouldn't be, which is arguably less common than failing to clean up on all code paths.

      ...if you program fails it still crashes.
      What's a catch block for then? For some classes of faults there's nothing sensible to do except scream at the user and move on. Resource exhaustion errors are probably the worst to try to recover from, as you may not have the resources left over to properly recover.
      Bad logic is bad logic no matter how "safe" the language is.
      Agreed there; inadequate validation and/or containment of input is another common class of exploitable bugs.
      --
      ...when you're writing a game...tweak the difficulty of "Easy" to something [your mother] can cope with. -- onion2k
    72. Re:Too late Java is not cool anymore by owlstead · · Score: 1

      I almost agree about the portability of Swing (the Java User Interface Widgets for non-Java users. The problem with it is that it tries to emulate Windows Widgets. Doing so means that it is always just *not* being the real thing. Anyway, for some stupid reason, applications do not seem to default to the Windows look on Windows, which is just plain stupid. The idea that you can emulate toolkit is just plain stupid.

      The Eclipse SWT toolkit does a much better job. It uses more of the hosts widgets, while still implementing most of its usability in Java. It's more responsive, and more and more apps are written for it, including things like Azureus, a well known bittorrent client.

    73. Re:Too late Java is not cool anymore by owlstead · · Score: 1

      Eclipse and Azureus both use the SWT widget toolkit, which comprises of a Java interface to widgets. It does therefore need specific platform specific libraries, though it seems to be pretty easy to port. Windows, Linux and Apple are all supported, though Windows does seem to be the front runner for new features. SWT is NOT included in the default Java packages from Sun, but can be downloaded from eclipse.org (a former IBM division split up, with lots of support from the community, except for Sun).

    74. Re:Too late Java is not cool anymore by stoborrobots · · Score: 1

      GCJ for MingW

      HTH. HAND. Cheers.

    75. Re:Too late Java is not cool anymore by Decaff · · Score: 1

      The idea that you can emulate toolkit is just plain stupid.

      Neither Sun or Microsoft agree. On Longhorn, Swing will look exactly like native Windows.

      The Eclipse SWT toolkit does a much better job.

      The default Windows distribution of SWT does a far worse job, and doesn't use the XP style.

      It's more responsive,

      There have been recent complaints about SWT performance, especially on Linux. The latest implementations of Swing in Java 5.0 are often faster.

      and more and more apps are written for it,

      My impression is that SWT is not that much used (as you can tell by the lack of XP support).

    76. Re:Too late Java is not cool anymore by Mock · · Score: 1

      While I agree with you that there are parts of java that can be made better by open-sourcing it (getting rid of those BLOODY checked exceptions or perhaps burying Calendar since the Aztecs have no month of June), I believe you are missing the big picture.

      Look at the advances in all of the ISO-specified languages. I'll use C++ as an example.
      Look at the YEARS (almost 10) it took to incorporate templates after they were first proposed. The boost library innovations are adopted at a snail's pace by the ISO committee.
      And for the C programming language, our most recent incarnation is C9X, called that because they kept missing their deadline.

      And these are the fast moving ISO/IEEE languages!

      Now look at Java. Steady releases of the reference JVM, lots of developer feedback. And just now we got Java 1.5 with all the generics, auto-boxing, and annotation goodness, just over 3 years after Java 1.4.

      One of the reasons Sun wants to retain control of Java is because releasing it to open source will also expose it to the ISO and IEEE committees, and that's a surefire way to stifle innovation in the language.

      There's also the issue of Microsoft.
      Once Java is released as open source, Sun has no legal standing against Microsoft trying to embrace and extend again. Bill would love nothing more than to see Java bogged down and pushed into obscurity.

    77. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Neither Sun or Microsoft agree. On Longhorn, Swing will look exactly like native Windows.

      (c) Sun Marketing 1999 (with "Longhorn" replaced by the various versions of Windows). Sun has been promising that the next version of Java will sort out all the problems and make everything right ever since they superseded AWT. It's never happened... and they've always proved to be full of shit. Why should anyone believe them now?

      There have been recent complaints about SWT performance, especially on Linux. The latest implementations of Swing in Java 5.0 are often faster.

      Lie. There are lots of niggles with SWT. Slower than Swing under Linux isn't one of them... indeed slower than Swing under Linux would require the use of some type of time machine.

      My impression is that SWT is not that much used (as you can tell by the lack of XP support).

      My impression of Swing is that it's not used much.

    78. Re:Too late Java is not cool anymore by Decaff · · Score: 1

      (c) Sun Marketing 1999 (with "Longhorn" replaced by the various versions of Windows). Sun has been promising that the next version of Java will sort out all the problems and make everything right ever since they superseded AWT. It's never happened... and they've always proved to be full of shit. Why should anyone believe them now?

      Because they actually shown it working in the Mustang Java build.

      Lie. There are lots of niggles with SWT. Slower than Swing under Linux isn't one of them... indeed slower than Swing under Linux would require the use of some type of time machine.

      Why do posters have to be so abusive?

      This speed issue is well established:

      Eclipse bug 37683: "Address platform-specific UI performance problems."

      "There is a noticable UI performance and responsiveness difference between Eclipse running on Windows and Eclipse running on Linux GTK, Linux Motif, or QNX Photon, all on the same hardware, with Windows clearly outperforming the others."

      Eclipse uses SWT.

      My impression of Swing is that it's not used much.

      Your impression is wrong. Just check job sites.

    79. Re:Too late Java is not cool anymore by njcoder · · Score: 1
      "Eventually, Java will become open source once Sun is bought, probably either by IBM or RedHat."

      RedHat buying Sun? How can anyone take what you say seriously when you say something as stupid as this?

      RedHat's market cap is only around 2 billion dollars. Sun still has enough cash to buy RedHat up even after spending 4.1 billion on StorageTek. RedHat's yearly revenue is only about $125,000,000. Sun's is close to $3,000,000,000. RedHat only has about $300 Million in cash and short term investments.

      Sun's market cap is about $12 Billion. IBM could probably buy them but it wouldn't be cheap and their stockholders would be too happy about it because they'll be paying a large premium for what they really want, which is Java.

      Best thing for IBM, RedHat and to do, is to continue to work together closely and stop all the nagging and mudslinging. The server market is big enough for IBM and Sun. The OS Market is big enough for Solaris, RedHat and AIX. They should notice that Windows server sales finally surpassed Unix sales recently and concentrate on keeping the Unix market growing as a whole, so that they don't have to fight over what crumbs MS leaves behind in the future.

    80. Re:Too late Java is not cool anymore by Trix · · Score: 1

      Only Sun can make Java(tm).

      Those who trust in sole-source products, reap what they sew.

      --
      I want all of the power and none of the responsibility.
    81. Re:Too late Java is not cool anymore by Trix · · Score: 1

      Yeah, yeah, I know:

      s/sew/sow/

      I knew it was wrong in the preview and hit [Submit] anyway.

      Pobody's Nerfect.

      --
      I want all of the power and none of the responsibility.
    82. Re:Too late Java is not cool anymore by civilizedINTENSITY · · Score: 1

      Ok, maybe not RedHat, but what about Apple?

      "Sun's market cap is about $12 B."
      But Apple's market cap is about $30.57 B.

      "Sun's yearly revenue is about $3 B."(Its really more like 11.21B)
      But Apple's revenue is 11.10B.

      And Sun's Net Income is about 651.00M.
      Apples Net Income is about 752.00M.

      So what about Price to Earnings? (P/E)
      Sun about 19.02,
      Apple about 40.64
      (DELL about 30.82, HP 19.51)

    83. Re:Too late Java is not cool anymore by njcoder · · Score: 1
      I don't think Apple is big enough to buy Sun either. If anything would happen it would be more like a merger. Apple doesn't have that much cash on hand and it would have to involve a stock transaction. My mistake on revenue. I was looking at quarterly data by mistake.

      I'm not sure how a larger P/E figures into being a worthy buyer. My opinion on P/E is that it's an indicator for how much faith the market has for a company.

      I'm not sure how well Sun and Apple would merge either. Not to mention having Scott McNealy and Steve Jobs under the same roof.

      If someone told me that Sun was going to get bought, my first guess would be that Nokia was making the bid.

    84. Re:Too late Java is not cool anymore by SparafucileMan · · Score: 1

      to whatever java fag moded me down, come find me when you grow balls and loose your virginity.

      java is a pointless, stupid language. it's no harder than C++, yet far worse in every way.

      for gods sakes...

      whoever, out of all the languages on earth, chooses java as their prefered one... should be shot. or should go to a titty bar before its too late.

    85. Re:Too late Java is not cool anymore by cubicleman · · Score: 1

      I still don't see what advantage(s) have Java open-sourced would bring. I've been developing substantial server-side applications in Java since '95 (pretty much my exclusive language since then, except for a brief foray into C and Perl on one project in '02). I see the utility of and use various open source libraries and applications for Java (JBOSS, Apache Commons, etc), but Java itself?

    86. Re:Too late Java is not cool anymore by mwvdlee · · Score: 1

      Because, as you mention yourself, bad products in Java are the result of bad programmers, not a bad language.
      Besides, you don't judge the C++ language by the way that Windows' implements it's GUI API's either.

      --
      Slashdot social media options: AIM, ICQ, Yahoo, Jabber and Mobile Text. Why no MySpace?
    87. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      P.S.: You're obviously bullshitting if you say "I don't find any java app to be slow".

      Either that you've never installed Oracle, or used Suns Patch management tools, or used the java solaris installer, or used eclipse...or any number of other applications...


      Time to upgrade that 386 of yours.

    88. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Because they actually shown it working in the Mustang Java build.

      No, they have not.

      Why do posters have to be so abusive?

      Probably because you continue to dodge and evade...

      This speed issue is well established:

      Eclipse bug 37683: "Address platform-specific UI performance problems."

      "There is a noticable UI performance and responsiveness difference between Eclipse running on Windows and Eclipse running on Linux GTK, Linux Motif, or QNX Photon, all on the same hardware, with Windows clearly outperforming the others."

      Case in point. You made a specific claim that Swing was faster on Linux than SWT and cite this to back it up. It's not, and your quote is irrelevant. SWT is slower on Linux than it is on Windows, but SWT is a hell of a lot faster than Swing. I don't think you realise just how bad Swing is -- particularly on Linux. Like the original poster said, you live in your own little world of Sun marketing.

      Your impression is wrong. Just check job sites.

      I have done. My impression of Swing is that it's not used much.

    89. Re:Too late Java is not cool anymore by Decaff · · Score: 1

      Because they actually shown it working in the Mustang Java build.

      No, they have not.


      Yes, they have. You will find parts of it already working in the current Mustang beta.

      Case in point. You made a specific claim that Swing was faster on Linux than SWT and cite this to back it up. It's not, and your quote is irrelevant. SWT is slower on Linux than it is on Windows, but SWT is a hell of a lot faster than Swing.

      No, I said: "The latest implementations of Swing in Java 5.0 are often faster.". I made no claim for general better performance. My link showed that there were serious complains about SWT performance on Linux. There are no complains about NetBeans performance on Linux (which uses Swing).

      If developers are complaining so much about SWT performance on Linux that it is down as a bug, but are not complaining about NetBeans/Swing on Linux (indeed, it wins an award), that backs my point.

      I don't think you realise just how bad Swing is -- particularly on Linux. Like the originaI poster said, you live in your own little world of Sun marketing.

      Wrong. I develop Swing applications which are deployed on Linux and I used Swing applications on Linux, so I know.

      Swing used to be a real problem on Linux - I would have agreed that it was terrible, but that was years ago. With later Java 1.4.x releases, and now with Java 1.5.x, it is crisp and fast (or at least that is the impression I get and my users get).

    90. Re:Too late Java is not cool anymore by Anonymous Coward · · Score: 0

      Yes, they have. You will find parts of it already working in the current Mustang beta.

      Heard (and seen) it all before... come back when there's a working version out there and general users and developers don't go "urghh" whenever a Java app loads.

      There are no complains about NetBeans performance on Linux (which uses Swing).

      Splutter... I'm sorry I'm desperately trying to stiffle the giggles here. That may be the single biggest humbug you've yet posted. Anyone who can seriously say that there are no complaints about the performance of NetBeans on Linux *is* lying.

      Wrong. I develop Swing applications which are deployed on Linux and I used Swing applications on Linux, so I know.

      Oh, if you look hard enough you can find some deluded halfwit who uses Swing, or a poor unforunate peon who through corporate politics is forced to write Swing apps... but the usage of Swing is so low as to be all but invisible.

      Swing used to be a real problem on Linux - I would have agreed that it was terrible, but that was years ago.

      No... Swing before 1.4 was so bad you simply couldn't even run a Swing app. Writing one was a job for a crackpot. After 1.4 Swing was merely awful. A significant improvement, I'll grant you. 1.5 hasn't made any significant improvements as far as I can see. Under Linux it's still *really* bad -- even though it now has a crappy gtk plaf.

      With later Java 1.4.x releases, and now with Java 1.5.x, it is crisp and fast (or at least that is the impression I get and my users get).

      You truly do live in a wibbly-wobbly world of your own. You stagger me with your delusion.

    91. Re:Too late Java is not cool anymore by Decaff · · Score: 1

      You truly do live in a wibbly-wobbly world of your own. You stagger me with your delusion.

      I have a suggestion. Why not back up your arguments with evidence, not insults?

      I'm not suggesting you have not had bad problems with Swing. We all have. However, you seem to be extrapolating your experience to others and stating that anyone who does not claim to share your point of view is 'lying' or 'deluded'.

      I don't think this is helpful in backing your case. For example, I mentioned that NetBeans (a Swing application had won an award from developers. Thousands of developers considered it to be a fine application that was easy to use and fast. You almost certainly don't agree with them. Fine. but to label them all 'deluded halfwits' makes you look bad, not them.

      If you wish to have a reasoned debate, don't post as anonymous, and back your points of view with actual evidence. Until then, you are only posting opinion and insults, not anything worth replying to.

    92. Re:Too late Java is not cool anymore by alucinor · · Score: 1
      RedHat buying Sun? How can anyone take what you say seriously when you say something as stupid as this?

      Yeah, you're probably right; I was just making a wild guess, and have my head down in code too much to really pay attention to stocks. I was just trying to think of companies with an interest in Java, but as someone mentioned Nokia, that sounds like the best bet yet.

      --
      random underscore blankspace at ya know hoo dot comedy.
    93. Re:Too late Java is not cool anymore by Snaller · · Score: 1

      Being slow is a consequence of today's complexity and modern development techniques...

      Actually its a case of sloppy development. They don't care about making the programs fast, so you don't get that.

      you simply can't say "Java" and expect it to mean "slow".


      Oh yes I can.

      --
      If Google really cared they would fix Android Chrome to reflow text, instead of discriminating
    94. Re:Too late Java is not cool anymore by njcoder · · Score: 1
      "but as someone mentioned Nokia, that sounds like the best bet yet."

      Yeah, that guy sure seems to know his shit :)

    95. Re:Too late Java is not cool anymore by crazyphilman · · Score: 1

      Java's plenty cool. But now, there are alternatives. Look at the .Net languages; they're practically clones of Java, with tweaks and a much easier GUI programming system. Look at it from another perspective, I know you're probably into Java, but consider this:

      With Java, you're stuck with AWT, Swing, or SWT (SWT is probably the best option, but it's not pure Java, is it? It's got chunks that are platform specific, so you have to compile for a specific platform). If you want to use an IDE, you have a few to choose from, but I wouldn't consider any of them to be all that good (Eclipse seems pretty nice, but it doesn't do all the grunt work that Visual Studio does). Web development with Java is complex and weird, with too many competing methodologies.

      Maybe people are just getting tired out, what with all the details they have to worry about.

      Now look at something like PhP. Simple, clean, works just fine for all normal-sized sites (i.e. everything short of an international banking system)... Easy to learn, easy to work with.

      Then there are the other scripting languages. Perl, Python, Ruby... All are easier to work with than Java, and let you do approximately the same things. Actually, their string processing beats Java's hands down, and as the old Unix guys used to say "every program is a filter".

      And look at C#. C# is so Java-like it could be Java's fraternal twin. And look how easy the developer's tools are to work with. Everything just flows, you can focus on your actual problems instead of frameworks, Javabeans, plumbing...

      C# is now an open-source project (Mono)! It's an ECMA standard! It's free for everybody to download and use on their Linux boxes, complete with an IDE (MonoDevelop)! It's got an amazing GUI designer (Glade) which produces XML files containing all the event mapping, which your program can just wave a magic wand over. You can do real programming just by coding the event handlers, and you can pass the same XML file around to different people to use with different compilers, languages, etc -- that's freakin' AMAZING. Think about the implications of this: you can have an arty-farty guy build your GUI to look gorgeous, and all you as a developer need from him is the XML file; you can read off the list of event handlers and start coding. The whole idea is amazing.

      Don't take it so personally. All it means is that Java is "just another language" now. This is a GOOD thing.

      --
      Farewell! It's been a fine buncha years!
    96. Re:Too late Java is not cool anymore by crazyphilman · · Score: 1

      Is "loose your virginity" like "loose the hounds"? Does it run barking into the night, pursuing a fleeing coed?

      --
      Farewell! It's been a fine buncha years!
    97. Re:Too late Java is not cool anymore by afd8856 · · Score: 1

      I'd rather have slow products that have lots of features that I need then fast products with only a fraction of what I need.

      (Of course, this doesn't apply every time).

      --
      I'll do the stupid thing first and then you shy people follow...
    98. Re:Too late Java is not cool anymore by civilizedINTENSITY · · Score: 1

      I wasn't so much suggesting a synergy, as pointing out that Apple is sitting pretty when compared to Sun's financial records. I thought that might surprise some slashdotters.

    99. Re:Too late Java is not cool anymore by civilizedINTENSITY · · Score: 1

      Oh, and 2,969,000,000 cash isn't bad (end of 2004). Call it 3 Billion. Cash And Cash Equivalents, plus Short Term Investments (where you put cash so it isn't losing to inflation, but still retains liquidity), bumps them to like 5.5 Billion. That is about 1/2 of Sun's market cap, just out of their liquid assets. I'd say that if for some reason (God help them) they *wanted* to buy Sun, it wouldn't be hard for them.

  3. And Again by AKAImBatman · · Score: 5, Interesting

    Java: One Step Closer To Open Source

    *sigh* Sun is already as open as they're going to go with Java by releasing it under the Java Research License. Now Sun has never complained about or hawked Open Source JVMs, but neither have they been too keen on helping out projects who bite their hands. As a result, the project to watch is the Apache Harmony Project. Given that Apache maintains a close relationship with Sun, hasn't burned their bridges, and has a good track record for completing very complex software, there's a good chance that the Apache JVM will quickly exceed Kaffe and GCJ.

    1. Re:And Again by Anonymous Coward · · Score: 1, Insightful

      neither have they been too keen on helping out projects who bite their hands. As a result, the project to watch is the Apache Harmony Project. Given that Apache maintains a close relationship with Sun, hasn't burned their bridges,

      The fact that ability to work with Java is based on how politically friendly your organization is to Sun seems, to me, to be the primary problem with the Java licensing situation. Look at Perl or Python or any number of "open source" languages, and your ability to work with, package, resell embed etc the langauge is in no way restricted by your ability to get along with Larry Wall or whoever. Now notice how those languages are flourishing in a lot of situations where Java is right now having problems.

      This is, in fact, probably the primary advantage of open source, that the success of the product is not dependent on the behavior of the vendor, and the more I see situations like this (Java being held back in some situation because of something Sun did) the more I begin to see what the fanatic GNU hippies were talking about in the first place.

      As a developer, I don't give a shit whose bridges with Sun are and aren't burned. I expect Sun to do whatever is necessary to make their product useful to me and Sun's other customers. That includes maximizing the ubiquity, growth and flexibility of the language. If that involves having *gasp* to actually work with organizations they're unfriendly with, then they either better well damn either do it or choose a licensing model which allows other organizations to grow the Java platform without Sun's help. If Sun can't do what is necessary to make their product the best one available, then at some point I'm going to have to look into the fact that I have other alternatives.

      Anyway the license you cite is listed as being

      as subject matter for learning and research

      That's nice, but it isn't very useful for those of us who eventually have to get things done in the real world.

      - Posted as anonymous coward because as a developer I have a business relationship with Sun, and I've seen what happens to people who "burn their bridges"!

    2. Re:And Again by Anonymous Coward · · Score: 1, Informative
      there's a good chance that the Apache JVM will quickly exceed Kaffe and GCJ
      You do know that major developers from Kaffe (Dalibor Topic) and GCJ (Tom Tromey) are actually part of the Harmony effort? The whole idea of the project was to work together (get the name?). Apache Harmony is currently bug free because they don't have any code. And it might very well be that they will stay bug free. The project is about cooperation and discussion of (research) ideas. Kaffe, GCJ and especially GNU Classpath is where the actual code will be produced. Rebranding it to Apache Harmony will certainly be done as a good marketing move. But everybody involved really doesn't see this as competition. Don't get fooled by people who want to see opposites everywhere. Real free software hackers work together!

      For some facts please read The Apache Harmony Blog

    3. Re:And Again by Anonymous Coward · · Score: 0

      Given that Apache maintains a close relationship with Sun, hasn't burned their bridges, and has a good track record for completing very complex software, there's a good chance that the Apache JVM will quickly exceed Kaffe and GCJ.

      So how cosy you are with Sun affects how successful you are with Java? Sounds like the Sun detractors have a point.

    4. Re:And Again by AKAImBatman · · Score: 1

      The fact that ability to work with Java is based on how politically friendly your organization is to Sun seems, to me, to be the primary problem with the Java licensing situation.

      That's just a load of nonsense. If you want someone to offer help, it is generally wise not to piss them off. From day one, the OSS community has badgered and berated Sun. Sun has attempted to appease them, but certainly isn't going to go out of their way for someone who's effectively declared themselves an enemy.

      So, Mr. AC. I think you're a loser and a jackass, you never say anything insightful, you're worthless, and you shouldn't even exist. Could I get you to lend me 50 bucks?

      Get the point?

      Keep in mind that Sun has been *really* nice to OSS projects in spite of themselves. AFAIK, they have never complained about the Kaffe or GCJ projects, never attempted to put barriers in the way, and tried to offer up as much information as possible. Look at the new JRL! It explicitly allows you to remember and reimplement anything you learn (one of the greatest criticisms of the previous license). Sun never intended to sue an OSS project because of things they learned from SCSL code, and have since clarified their position. That helps close the supposed holes in documentation that Kaffe and GCJ claim to exist. (Whatever they are, I certainly haven't seen them.)

      As a developer, I don't give a shit whose bridges with Sun are and aren't burned. [...] Posted as anonymous coward because as a developer I have a business relationship with Sun

      Oh the hypocrisy. Are you sure you aren't just trolling?

    5. Re:And Again by njcoder · · Score: 2, Interesting

      There might be problems surrounding the Apache Harmony project. Geir Magnusson now works for IBM. When Sun talks about a fear of forking Java like Microsoft did, they aren't worried about MS now, they're worried about IBM.

    6. Re:And Again by Anonymous Coward · · Score: 0

      Quoting from the proposal http://mail-archives.apache.org/mod_mbox/incubator -harmony-dev/200505.mbox/%3C3923A844-DEC5-4CC2-ADE D-B1F144BB6AF5@apache.org%3E:

      "We will create directly, via inclusion of independent third-party code, or through contribution :

      a) a freely implementable specification of a modular VM and class library that allows for multiple, independent implementations

      b) a test suite for interoperability testing of the modules

      c) an implementation under the Apache License of the modular VM [...]."

    7. Re:And Again by DaliborTopic · · Score: 1

      Fixing the license incompatibilities between the GPL and Apache License are on the agenda as well, as obviously everyone would like the GPLd runtimes to be able to reuse code written within Apache Harmony. cheers, dalibor topic

    8. Re:And Again by DaliborTopic · · Score: 1

      I am not aware of Kaffe, or gcj, or GNU Classpath biting Sun hands, at least noone at Sun told me that, and I've talked with Schwartz, Gosling, and a lot of other folks there ... The Kaffe.org project is not affiliated with Sun Microsystems, so there are no hands involved which could be bitten, afaict. It is also not a 'J'VM, as the term 'JVM' is trademarked by Sun Microsystems for their proprietary software offerings, so I don't use that and wouldn't recommend using it. Kaffe is a VM, no sugar for me, thanks. cheers, dalibor topic

    9. Re:And Again by DaliborTopic · · Score: 1
      Given that Sun Microsystems is a large part of the "OSS community" (see the "share" marketing campaign going on atm), that you accuse of pissing off Sun, you make it sound as if that they have done a lot of bad things to themselves. Have they, really? I'd find that odd.

      "effectively declared themselves an enemy", oh my goodness, that's a really odd phrase. Where did you get that sort of weird, martial language from? What makes you think it fits software development, or what Sun thinks of Free Runtimes?

      There had been almost no contact between Sun and the Free Runtimes for the first 9 years, until a few folks (including me) started building bridges last year, and working together with progressive people inside Sun Microsystems on finding ways for Sun to learn to know the amazing stuff happening out there. There were no bridges to burn since Sun has never, afaik, tried talking to Free Runtime developers in the past. Sun has been largely non-existant in Free Runtime community, other then as a potential legal boogeyman, and that's certainly not because Sun didn't know where we're hiding. They probably simply didn't think much about it all. :)

      See, no Classpath devs care about begging Sun for favours, like asking for opening up their implementation. It's never going to happen, so why bother?

      What we're interested in is creating an ecosystem of great, mutually compatible runtimes for programs written in the Java programming language. In oder to fulfill the promise of the platform independance, and truely make programs written in the Java programming languiage run everywhere, we need to be fully compatible with the non-free implementations. It is in the interest of the non-free implementation vendors to be compatible with GNU Classpath.

      So mutual compatiblity is definitely an area that we can work on together. Where we differ is that at GNU Classpath, people are interested in verifiable compatiblity claims, rather than cute coffee cup logos, so Mauve, the GNU Classpath compatibility test suite is Free Software, that anyone, including Sun, can freely use to verify the compatiblity of their implementation with GNU Classpath. Sun has so far not returned the favour, they have instead chosen to release their test suites under non-free software licenses. It's their code, it's their choice, it's their loss.

      I keep saying that Sun is cordially invited to participate in GNU Classpath, whenever they are ready for it. I sincerely hope that Apache Harmony will be a good venue for them to become a part of the Free Runtime family, and collaborate with Free Runtime developers on shaping the future of the platform.

      Yes, I've looked at the new JRL, and unfortunately it's not as simple as the FAQs say. See http://www.mail-archive.com/classpath@gnu.org/msg0 9825.html for details. In particular, let me quote from Larry Rosen's book on open source licensing, regarding an almost word for word equivalent provision in Microsoft's Shared Source license:

      ""If you are a software developer who intends to write software that might potentially compete with Microsoft's copyrights or patents, there is great risk in looking at Microsoft's source code. Under the copyright law in the United States, if Microsoft proves that there is "substantial similarity" between your commercial software and theirs, you may be an infringer. You may have to prove that you saw and read Microsoft's source code but that you relied only on intangibles and only on your memory when you wrote your own software.

      That's a difficult evidentiary burden. I'm not sure how even an experienced programmer can walk that fine line. Perhaps the best way is simply not to look at Microsoft's source code at all."

      For another lawyer's optinion why you should stay away from Shared Source licenses like the JRL even if they may have been written with best intentions regarding tainting, see

    10. Re:And Again by AKAImBatman · · Score: 1

      Hi Dalibor,

      I am not aware of Kaffe, or gcj, or GNU Classpath biting Sun hands

      Kaffe accepts donations from Microsoft to implement Microsoft's contested extensions.

      The leader of the Free Software Foundation (under whom GCJ/Classpath is developed) starts an uncalled for flamewar over Java's status.

      Sun could easily "punish" projects for stuff like this (through more restrictive licenses, withholding key information from the public, etc.), but they don't. They're nice people, not intending to throw up any barriers. Yet time and again they are painted as an evil entity to be defeated for no reason what-so-ever. Thankfully, cooler heads usually prevail. Unfortunately, these cooler heads are usually not the OSS community or fan base. :-/

    11. Re:And Again by AKAImBatman · · Score: 1

      Given that Sun Microsystems is a large part of the "OSS community" (see the "share" marketing campaign going on atm), that you accuse of pissing off Sun, you make it sound as if that they have done a lot of bad things to themselves. Have they, really? I'd find that odd.

      Hardly. Sun has attempted to *enter* the OSS community time and time again, but they are consistently rebuffed and have to work on their own. They are even persecuted for their kindness! In general, IBM has done far less, but they get a free ride. Why is that?

      Yes, I've looked at the new JRL, and unfortunately it's not as simple as the FAQs say. See http://www.mail-archive.com/classpath@gnu.org/msg0 9825.html for details.

      Yes, I've seen your analysis. I find it overly critical, but I'm afraid I can do nothing to change that. Sun could probably sue you for hundreds of little infractions that the law may or may provide them with relief for. But they don't, because they are attempting to play nice. Sun may not have the motto, "do no evil", but their actions generally speak to it.

      For how bad things can go with Sun and open source projects not paying respect to Sun's licenses, see Lutris' Enhydra (open source application server from a few years ago, killed by its authors because of alleged SCSL violations),

      As I remember the situation, Sun never threatened legal action. Rather, Enhydra felt that they needed the Java Logo, and was going through the long process of obtaining the logo. Nor did that kill Enhydra. After the release of J2EE, lack of interest in their existing platform managed that. (Anyone remember ExoOffice?)

      JBoss (open source application server, had to fork over a certain, large amount of dollars to reach license peace with Sun)

      Sun made the TCK available to OSS projects, but JBoss is a commercial entity. In any case, things were always complicated there. (Never did get the full story behind why Rickard left.)

      On a side note, I plan to work with Sun's legal to see if their standard tainting clause could not be clarified, eventually, but don't count on it: I don't write Sun's licenses, Sun does.

      That's good news. :-)

      Regarding missing documentation, well here is one for you: javax.swing.text.html.HTMLEditorKit: can you tell which HTML 4.0 tags are supported and which are not supported, precisely, from the API specification alone? :)

      No, but I would take one of two tacks:

      1. Just support common tags and hope you're compatible enough. (This isn't as bad of an option as it may seem at first. Even if you get a few details wrong, bug reports will help you sort things out later.)

      2. Test the existing Java binaries for what they are and are not compatible for.

    12. Re:And Again by DaliborTopic · · Score: 1
      I am afraid you've got Transvirtual, the company, and Kaffe.org, a free software project mixed up. It was Transvirtual that accepted funding from Microsoft, not the Kaffe.org project.

      Please take some time to read the Java Trap article, and you may find that it's a reasonable, informed opinion about the importance of using Free Software as building bricks for Free Software, rather than introducing hidden dependencies on non-free software. RMS encourages people writing Free Software to evaluate their choices. If they chose the Java programming language they are encouraged to test their code with Free Runtimes, and to help along to make them preferable choices for development and execution of programs written in that language to the non-free implementations. My experience from a few exchanges with RMS is that he's too polite (and busy) to engage himself in flamewars.

      A more restrictive licensing arrangement of Sun's source code would hurt Sun Microsystems more than anyone else, as no Free Runtime licenses source code from Sun Microsystems, so they can not be affected by whatever license Sun, if they were as childish as you seem to believe, came up with.

      Withholding key information from the public is not possible for Sun any more, now that the JCP takes care about the specifications. Making specifications deliberately worse than they are would again be a move that would only hurt Sun and their customers.

      There is nothing evil about Sun Microsystems. They are a huge corporation worth billions of dollars and certainly not shaking in their boots and contemplating desperate measures just because a bunch of hackers managed to pull off what was thought to be impossible and create a thriving ecosystem for Free Runtimes around GNU Classpath or because a few years ago some company made a deal with Sun's current most valued business partner.

      I'd be interested to know what makes you think that Sun's so desperate.

      cheers, dalibor topic

    13. Re:And Again by AKAImBatman · · Score: 1

      I am afraid you've got Transvirtual, the company, and Kaffe.org, a free software project mixed up. It was Transvirtual that accepted funding from Microsoft, not the Kaffe.org project.

      *raises eyebrow*

      Kaffe was Transvirtual's baby. It may be relatively independent now, but it certainly wasn't back then. Speaking of which, where did Transvirtual go? Kaffe/Transvirtual sort of disappeared for a while, and by the time Kaffe started making news again, there was no sign of Transvirtual.

      Please take some time to read the Java Trap article, and you may find that it's a reasonable, informed opinion about the importance of using Free Software as building bricks for Free Software, rather than introducing hidden dependencies on non-free software.

      I have read it, and it's mostly nonsense. I understand Mr. Stallman has his opinions, but I did not appreciate how he stirred the pot with "The Java Trap" or other press during the OOo debacle. As any good politician can tell you, you can quite easily stir things up while still being polite. And this isn't the first time Mr. Stallman has taken it upon himself to incite a flamewar. His hounding and later "I told you so" episode with BitKeeper was less than grown up, not to mention his hounding of the KDE project.

      In the past I have had nothing against Mr. Stallman, but for now at least, I'm a bit peeved about his behavior. Not only was the OOo Jihad unnecessary, the complaints floated were non-existent. OOo's "appeasment" was nothing more than what they had already done! It amazes me that OOo's use of Java since the beginning was okay, but as soon as Sun fixed the *real* problems (e.g. dependence on hidden APIs), everyone is all over them! As for "Sun Specific APIs", all I can say is, "They're in the fine manual." If Classpath doesn't have them implemented yet, that is not Sun's fault or the fault of the Java community. You're free to implement the missing functionality.

      Withholding key information from the public is not possible for Sun any more, now that the JCP takes care about the specifications.

      And who voluntarily create the JCP? Sun has had a great deal of power. While they've occasionally screwed up relationships with developers (e.g. the FreeBSD Java issues), they have never taken direct action against any OSS project. Sun carries their responsibility and expects others to do so as well.

      I'd be interested to know what makes you think that Sun's so desperate.

      I'm not certain where you get the idea that Sun is desperate. I certainly never said or suggested such a thing. My point was only that Sun has had plenty of opportunities to crush OSS. They have not done so, will not do so, and will continue to foster its growth in the future. Despite all the pain, suffering, and outright bad press they receive at the hands of the OSS community as a whole.

    14. Re:And Again by DaliborTopic · · Score: 1
      I kindly refer you to sunsource.net FAQ for Sun's own statements regarding them being a part of the open source community. I'm sure they know best whether they are or are not a part of it. Or someone hacked the site. :)

      The OOo issue was largely a case a of miscommunication between FSF, Sun, various online publications, and bad PR firefighting. I don;t think anyone saw it coming until it surfaced in the Newforge article. And then wham! All hell was lose.

      See Fedora Core 4 for a nice OOo 1.9.x that runs well with gcj. See the tools-jdk list for the current discussions about OpenOffice.org support for Free Runtimes, and how to avoid such things in the future (build deamons with gcj, for example),

      I guess IBM gets a lot of sympathy for dealing with SCO. Heard anything crazy about GPL being an unamerican tool of terrorists from Darl lately? :) IBM's taking out the trash, and that's very kind of them, as it's not such a fun task.

      My analysis of the JRL is very critical for a simple reason: noone wants to have to go to court, in particular over something that could have been avoided easily by analysing the license and trying to figure out the worst case, and make sure that it does not occur. The legal opinions I quoted give a pretty good reasoning why one should avoid getting bound by simplistic Residual Rights clauses, I think, and why it is so hard to prove in court that no copyright infringement occured if it comes to a lawsuit. Why create potential copyright problems in the future, when we are doing fine without that source code? If one looks at the last three years, Free Runtimes have prospered nicely without having or demanding access to Sun's source code. I don't think that whatever information is buried in the source code if worth putting an aura of doubt around our efforts and potentially putting Sun into an uncomfortable position oh having to pick their alegiances. Instead, such information should find its way into the official specs.

      I think the SCSL is quite clear in that respect: when the Lutris developers accepted the SCSL, they were bound by it, and could not release their product os open source without violating the SCSL. There was no need for anyone to threaten anything as the issue is pretty clear cut, and if you read the enhydra archives from back then, it's pretty apparent that Enhydra App Server devs, after trying to negotiate with Sun about having a certified J2EE server under an open source license, gave up in frustration and chose to accept the SCSL and not to release their code as open source, rather then violating Sun's license. That's a very sane decision.

      The JBoss agreement is the most puzzling part of the SCSL puzzle, as most news sources from back then indicate that JBoss and Sun had to clean up some licensing problems, and that cleaning up was monetary. JBoss was shipping Sun's code licensed under the BCL, according to Marc Fleury http://www.theserverside.com/news/thread.tss?threa d_id=9177 . Afaict, BCL has some pretty heavy obligations as well regarding javax namespaces, and by developing Jboss for javax.* APIs and distributing BCLd code prohibiting subclassing of those APIs, they might have violated the BCL. Nevertheless, most news reports back then talked about the SCSL, so I need to say that I am just speculating here, as no official statements on the background of the whole deal were released by either side.

      If you've got a chance to get the javax.swing.text.html.HTMLEditorKit specification improved, please go for it, this was just meant as an example of the specs being somehwat incomplete. For a rather bad example, see RTFEditorKit.

      What one usually does with such incompletely specified classes is to see what other literature exists describing the missing details (books on SWING, for example), and how the code is used in real life by Free Software applications.

      cheers, dalibor topic

    15. Re:And Again by DaliborTopic · · Score: 1
      Transvirtual went straight into bankruptcy a few years ago. Afaict, the Kaffe.org project is independant, as there is no corporate backer throwing money at it. It's driven by energetic, fun people.

      I believe most of the stirring up regarding the Java Trap article was done by people who either did not read, or did not understand the article properly, and went off on wild tangents. Afair, RMS has not taken part in the ensuing flame wars.

      You misunderstood the OOo issue, but that's understandable. As I explained in other places, Sun, Free Runtime developers and OpenOffice.org developers have sat together to figure out a good way to plug different VMs into OpenOffice.org. Various people tried their luck making Free Runtimes work with OOo (I, for example, failed making sense out of the build system, and the com.sun.secret.and.unspecified.Something classes referenced in the sandbox module, and eventually gave up trying to figure the largely undocumented code out.). Caolan, otoh, didn't give up, and made gcj work well as a runtime within OpenOffice.org. That was cool, and he managed to get his patches gradually integrated into OOo's main tree. Then he went for holidays, someone published an article about Sun sneaking in Java in the next version of OOo and all hell broke lose without anyone having a real clue what was happening for the first day or two. Then it got fixed, but Caolan was still on holiday away from his mail, so noone was able to tell how far along things really are. It turned out that they are very far along, and as you can see for yourself in Fedora Core 4, most things just work.

      If you want to see Sun Specific APIs in action, please grep over the 1.0.x source code for imports of com.sun.* or sun.* namespaces. Those APIs are not specified, so they can not be implemented. See http://java.sun.com/products/jdk/faq/faq-sun-packa ges.html for details on why using Sun-specific APIs makes Java programs unportable and unreliable.

      If you take some time to research OOo on gcj, you'll notice that the development has been beneficial for both OOo and gcj. Good thngs can positively encourage each other, and OOo is a very cool project to help along with.

      I've got the idea that you are thinking that Sun is desparate from your continous stream of (mildly amusing) scenarious where Sun would be constrcuted to be threatening to me. They'd only run amok with funky IP claims if they were really, really desperate, though, as funky IP amok runs tend to leave the business in shambles as customers turn somewhere else. Sun is, these days, quite a few billions of dollars away from being desperate, though.

      I believe you're boxing with your own shadow, here. On one hand you're the one saying 'Sun could have crushed OSS! They could find many reasons to sue you, personally, even now!' on the other hand you're nevertheless saying 'Sun will never sue OSS projects. They never did.'. I think you are simultaneously arguing both sides of a heated 'Sun is evil! No it's not!' debate taking place somewhere else.

      You seem to take the pain, suffering, and (my goodness!) bad press that Sun gets pretty personally. Do you happen to work for Sun's PR team? Or are you by chance one of their Evangelists?

    16. Re:And Again by AKAImBatman · · Score: 1

      If you want to see Sun Specific APIs in action, please grep over the 1.0.x source code for imports of com.sun.* or sun.* namespaces. Those APIs are not specified, so they can not be implemented.

      I'm afraid you're misunderstanding me. As I said, Sun finally fixed these issues in the 2.0 series, yet that is where the charges are levied. I pointed that very fact out, and was ignored and pointed to 1.x references (as you yourself are doing). If someone wanted to raise a stink, they should have done it prior to 2.x - when the teams got things in order.

      I believe you're boxing with your own shadow, here. On one hand you're the one saying 'Sun could have crushed OSS! They could find many reasons to sue you, personally, even now!' on the other hand you're nevertheless saying 'Sun will never sue OSS projects. They never did.'. I think you are simultaneously arguing both sides of a heated 'Sun is evil! No it's not!' debate taking place somewhere else.

      Dalibor, you have a very strange way of twisting my words. Simply put, my point is that Sun has every reason to be pissed off, every method available to squash those who piss them off, and yet restrains themselves and works hard to be a "good guy". How you get opposing viewpoints from that, I have no idea.

      You seem to take the pain, suffering, and (my goodness!) bad press that Sun gets pretty personally. Do you happen to work for Sun's PR team? Or are you by chance one of their Evangelists?

      I do not work for Sun, but I am a longtime member of the Java Community. We've met before under the JL forums, but I've decided to withdraw my identity here.

    17. Re:And Again by DaliborTopic · · Score: 1
      You made the assertion that Sun Specific APIs do not exist, saying 'all I can say is, "They're in the fine manual."', I've shown that you are wrong: unspecified (com.)sun.* packages exist and they were unfortunately used in `1.0.x sources. Instead of raising a stink, people talked about it on the mailing list, filed bug reports, and things got fixed for 2.0.x. That's a good thing, and shows that developers are able to work together quite well.

      In my opinion, to go with the comic theme from your handle, you're painting Sun as some rather loaded, Hulk like character, that's every moment about to explode and go on a rampage in too tight shorts in an outburst of barely controlled rage.

      My experience is quite to the contrary. In this age of participation, as Schwartz calls it, Sun appears to be interested in positioning itself in the center of a social hub for creation of larger works, rather then posing as a potentially threatening bully outside the playfield.

      There is, simply put, no money to be made in squashing and threatening open source projects. It'd be an irrational act, and Sun is made up of pretty rational people, afaik. They seem to know what they are doing.

      cheers, dalibor topic

    18. Re:And Again by AKAImBatman · · Score: 1

      You made the assertion that Sun Specific APIs do not exist, saying 'all I can say is, "They're in the fine manual."'

      You're confusing two different points. The first one is that Sun Specific APIs no longer exist in OOo 2.0. The second point is that any valid APIs OOo uses are in TFM.

      In my opinion, to go with the comic theme from your handle, you're painting Sun as some rather loaded, Hulk like character, that's every moment about to explode and go on a rampage in too tight shorts in an outburst of barely controlled rage.

      No, you are painting them that way. Why you are, I have no idea. My point is clear enough. Your choice to ignore it is both confusing and frustrating.

  4. They... by Shads · · Score: 1

    ... just need to jump in both feet and get it done with.

    --
    Shadus
    1. Re:They... by oscartheduck · · Score: 0

      See, now, we can see it like that. But when you're a multi-billion company, the idea of moving away from the business model that has served you so well so far may seem more intimidating.

      --
      How to use coral cache: http://slashdot.org.nyud.net:8090/~oscartheduck
  5. Open Source Coffee? by LiquidCoooled · · Score: 0

    You mean I take my own equipment and have a picnic in the city centre?

    Are we going to have open source cakes and sandwiches as well?

    --
    liqbase :: faster than paper
  6. "Open Source" by Anonymous Coward · · Score: 5, Interesting

    If Sun really wanted to be helpful they could forget the application server and really forget the source, and just concentrate on making a less restrictive BINARY license for redistributors such as linux distributions. Java is being held back in the absence of something like Harmony, and that's just absolutely rediculous when the problem would be so easy to fix. Sun needs to come to terms with reality and realize that they need an installed base, not the other way around.

    1. Re:"Open Source" by omb · · Score: 1

      This point needs to be oft repeated to SUNs
      senior management and Gosling!

    2. Re:"Open Source" by Decaff · · Score: 1

      Java is being held back in the absence of something like Harmony,

      How is it being held back? It is the most in-demand language in the job market, and the de-facto standard language for major server-side development.

      and that's just absolutely rediculous when the problem would be so easy to fix.

      It is not easy to fix. There can be major licensing and patent problems to overcome in open-sourcing a huge project like Java. This is why it has taken them so long to open source Solaris.

    3. Re:"Open Source" by Anonymous Coward · · Score: 0

      It is not easy to fix. There can be major licensing and patent problems to overcome in open-sourcing a huge project like Java. This is why it has taken them so long to open source Solaris.

      Did you miss the part where the AC was talking about binary license and doesn't even care about source code? If Sun would make their Java JRE/JDK binary license more flexible, it would help them and people wanting to use Java more than anything. And this would be an easy fix.

    4. Re:"Open Source" by Decaff · · Score: 1

      Did you miss the part where the AC was talking about binary license and doesn't even care about source code? If Sun would make their Java JRE/JDK binary license more flexible, it would help them and people wanting to use Java more than anything. And this would be an easy fix.

      I did miss it. I still think that these matters are more complicated that people think.

    5. Re:"Open Source" by MSG · · Score: 1

      Even with a less restrictive binary license, most Linux distributions wouldn't include the software, and most Free Software developers would avoid the Java platform.

      An important part of the freedom to use software is the freedom to fix it when it's broken rather than wait on a vendor who may not be responsive to your problem.

    6. Re:"Open Source" by Anonymous Coward · · Score: 0

      I don't see how Sun is solidifying its position by releasing its customers source code without first soliciting their input on the matter. In what way does this engender trust in Sun as an industry partner?

  7. In other news... by k4_pacific · · Score: 3, Funny

    In other news, the Ford Motor Company announced today a bold new initiative to sell more cars. It seems that they will now be allowing customers to open the hood and tinker with the engine after buying the car. Ford expects this to increase the popularity of their cars and create a huge market for third-party add-ons.

    --
    Unknown host pong.
    1. Re:In other news... by CrazyWingman · · Score: 2, Interesting

      WTF is that supposed to mean? I assume that you're trying to flame other Slashdotters for being too optimistic about Sun open-sourcing Java. I don't think your analogy holds up at all, though.

      It has always been the case that one could open the hood of a car (be it Ford, GM, Toyota, or other) and pull hoses, reroute wires, change belts, or otherwise modify the engine mechanics. Ford may not encourage this with an ad campaign of, "Buy our cars because you can take them apart and reconfigure them!" but it is still the case that this is possible.

      The only way I can make your analogy make sense is by assuming you meant that the open-sourcing of Java would make no difference. One can, in fact, write her or his own set of classes, or even VM, and run Java programs using it. Sun does not currently run an ad campaign to the effect of, "Use Java because you can rewrite the VM!" but it is still the case that one can.

      I appologize if I have assumed wrongly about your post in the first place, and just ruined your comment by explicitly explaining it. I just find it so hard to figure out what people around here are trying to say recently.

    2. Re:In other news... by duncanIdaho.clone() · · Score: 2, Funny

      Fan belt demand sharply skyrockets as Slashdotters attempt to overclock their Ford boxen.

      --

      feints within feints, wheels within wheels

    3. Re:In other news... by Anonymous Coward · · Score: 0

      And in other, other news, researchers discover that metaphors and analogies don't bear close examination.

      They do get trotted out and modded up by morons though.

    4. Re:In other news... by CableModemSniper · · Score: 1

      You must be new here.

      --
      Why not fork?
    5. Re:In other news... by Austerity+Empowers · · Score: 1

      I'd probably want to buy a Ford again if that were the case. As it stands I think I'd rather have my head run through a cheese grater.

  8. ...Not gonna happen by Donniedarkness · · Score: 2, Insightful

    Sun will not go completely open-source. They already have JBoss, which is open-source... too bad that no one I know of uses it. Also, I doubt anyone would have used Platform Edition 9...unless they made it Open Source and promoted the hell out of it, which is why they are doing this. Everything will remain closed-source. *shrugs* just my 2 cents, though.

    --
    Earn a % of cash back from Newegg, Tiger Direct, Walmart.com, and more: http://www.mrrebates.com?refid=458505
  9. What about your fiirst born? by RealProgrammer · · Score: 5, Funny

    They already did that*.

    --
    * Well, mostly.

    --
    sigs, as if you care.
  10. Great... more stupid questions from management by pestilence669 · · Score: 4, Funny

    News articles, like this one, have a way of being read by my bosses who mistake their content entirely. "I just heard that Java is free, can you look into that?"

  11. problems with Java by brontus3927 · · Score: 1, Insightful

    Of course any discussion of Java isn't complete without someone bringing up that it's slow and bloated. I don't mind the speed, because I don't use any java applications that need to be all that fast. IANA programmer, but java seems to have a horrible leak in it. I have to shut down my freenet node and restart it about once per day because javaw.exe slowly nibbles away at the available memory and will routinely eat up 99% of the CPU usage. The highest the memory usage has gotten before I restarted is ~ 181MB. Over 10% of my total memory!

    1. Re:problems with Java by mmkkbb · · Score: 2, Informative

      That could be a leak in the freenet client, no?

      --
      -mkb
    2. Re:problems with Java by CodeMonkey4Hire · · Score: 2, Insightful

      If a program is written poorly it is possible for it to hold on to a lot of its objects (memory) because Java thinks the program is still using them. I think the easiest way to screw up (but not sure) is to keep a hash around with all of your objects in it. As long as the hash still references the objects, even if nothing else does, the memory will not be freed up. Have you tried killing off specific aplications that are using Java to see if you can find which program is hoarding all of the memory or are you pointing your finger at the Java VM?

      --

      Let's go Hurricanes!!! 2006 Stanley Cup Champions!!!
    3. Re:problems with Java by duncanIdaho.clone() · · Score: 1

      Most definitely. I can run Eclipse for days without restarting or noticable memory leak.

      Javaw.exe's size represents Java's foot print AND your code's memory usage.

      --

      feints within feints, wheels within wheels

    4. Re:problems with Java by Anonymous Coward · · Score: 1, Insightful

      IANA programmer, but java seems to have a horrible leak in it

      Obviously not. Because if you were a programmer, you'd know Java has garbage collection, which means you have to screw things up pretty badly to leak memory.

      That is far, FAR more likely to be a bug in Freenet.

    5. Re:problems with Java by brontus3927 · · Score: 1
      That sounds logical. It's definately the freenet client, because if I kill the Java VM, freenet throws up an error message about getting disconnected. That and I really only run one java client. I'll have to look through the config file to see if this can be remedied. As I said before, I'm not a programmer by any stretch of the word (I can write simple to midlevel macros in VBA, but that's it), and don't really understand how exactly a java client interfaces with a Java VM. I had figured if it was the fault of the freenet client, than that would be hogging the resources instead of java.

      So, in short: mod parent up!

    6. Re:problems with Java by Gruneun · · Score: 1

      Of course any discussion of Java isn't complete without someone bringing up that it's slow and bloated

      I think the reason this perception exists is that Java spends time assuming the resonsibility for significant background work, like garbage collection, that you would otherwise have to code yourself in other languages. There's nothing preventing you from doing that and, in fact, you'll generally see a performance gain when you use finalization.

      Admittedly, I let the JVM do most of the work, too, since most of my apps don't require the performance gain of coding that end. Somewhere along the tight software vs. cheap hardware flip, most programmers realized that the elegance previously required can be substituted for with another stick of RAM. If we went back to the mindset of truly elegant coding all the time, I don't think you would see quite the speed difference with Java.

    7. Re:problems with Java by atavus · · Score: 1

      And various versions of the packaged for Debian java like to chomp up 1.8G (yes G) of RAM for every little java app.

    8. Re:problems with Java by aug24 · · Score: 1

      What you have singularly failed to understand is that programmers can still write applications that don't let their objects out of scope, just like they can still write bugs. Even a given JVM might not work well cough**Microsoft**cough. Don't blame the language, blame the app and the implementation.

      Justin.

      --
      You're only jealous cos the little penguins are talking to me.
    9. Re:problems with Java by mcc · · Score: 3, Insightful

      This sounds like a problem with Freenet, not with Java. You can write code with memory leaks in any language. Java makes memory leaks a little harder, but it in no way makes memory leaks impossible. If you had a C program where the author forgot to call free() would you complain about the "leak" in C?

    10. Re:problems with Java by -brazil- · · Score: 1

      The "freenet client" you see in the task list is almost certainly nothing but a startup script, with the JVM task being the actual client. And I agree that it's quite definitely the fault of the freenet client code, not the JVM.

      --

      The illegal we do immediately. The unconstitutional takes a little longer.
      --Henry Kissinger

    11. Re:problems with Java by Anonymous Coward · · Score: 0

      Finalization can't replace the job of the GC in Java. It's pretty much useful only for freeing resources the GC can't reach (allocated through JNI or whatever).

      It has nothing to do with performance, and even if you could write destructors in Java, it probably wouldn't beat a decent generational GC for most work.

    12. Re:problems with Java by Gorath99 · · Score: 1
      IANA programmer, but java seems to have a horrible leak in it

      Obviously not. Because if you were a programmer, you'd know Java has garbage collection, which means you have to screw things up pretty badly to leak memory.

      That is far, FAR more likely to be a bug in Freenet.

      What? I hope you're not a programmer either, because while your conclusion is right, your reasoning sure isn't.

      The fact that the Java language has garbage collection doesn't mean that any particular VM - which are usually implemented in a different language, like C/C++ - uses garbage collection for its own memory management as well.

      Your argument that garbage collection makes it hard to get a memory leak actually suggests that the bug more likely lies with Freenet (which is implemented in Java) than with Sun's VM (which IIRC is implemented in C++).

      By the way, I do believe the bug lies with Freenet, but I do so because Sun's VM is very thoroughly tested and used in countless production systems while the same can't be said of Freenet.
    13. Re:problems with Java by Jesus_666 · · Score: 1

      Of course. A programming language should not allow the programmer to write code that might, under any circumstances, degrade the efficiency of the system or even cause mild unpleasantness to the user. The ideal language should have no memory management, no I/O and no syntax, except for DWIM. Hell, the entire OS should be made from a long string of DWIM. DWIM is the way of the future.

      --
      USE HOT GRITS WITH STATUE OF NATALIE PORTMAN (NAKED AND PETRIFIED)
    14. Re:problems with Java by mcc · · Score: 1

      The ideal language should have no memory management, no I/O and no syntax

      So Haskell, then?

    15. Re:problems with Java by ArmorFiend · · Score: 1

      If I'd been able to moderate you "-1 Wrong", I would have, but I can't, so I'll just respond instead:

      It sounds to me like the grandparent is complaining that the garbage collector doesn't collect garbage. C's garbage collector is the app programmer, and if its not getting taken out that's the fault of the app programmer. C's GC is built in the language, and if the garbage isn't getting taken out, that's the fault of the language implementation. So, I blame the Java runtime, just like the grandparent.

    16. Re:problems with Java by Anonymous Coward · · Score: 0

      You are also wrong.... well, maybe.

      Having a garbage collector will not insure you against all memory leaks. You can easily write a program, build up huge arrays, list, String, etc. and hog the CPU.

      The GC can only do it's job is you release all references to objects. If you don't, memory will not be freed.

    17. Re:problems with Java by StarsAreAlsoFire · · Score: 1

      And it should electrocute the user when he does something wrong... like type.

    18. Re:problems with Java by StarsAreAlsoFire · · Score: 1

      Nope. Freenet is not unlinking objects -- not technically a memory leak, but same effect. Essentially, freenet is saying 'hey, Garbage collector! I'm still using this stuff, don't delete it for me, 'k?'

      There are cases where you must explicitly set objects to null if you want them to die; for instance, in a persistent object which spawns many children. Or in a complex object that has children of its own were parent is a member of child and child is a member of parent (something that simple will be found, usually, but it is the idea of 'ghost references' (correct term? someone?)).

      The easiest way to create something that looks like a memory leak is to keep adding stuff to a buffer or hashtable of some sort. I've crashed a prog by reading a file into a string buffer without worrying about size -- well, read in three files that are 20 megs in size and *poof* your JVM kisses you goodnight.

      Keep adding objects into a collection and don't delete them when you are done with them and guess what? It looks like a memory leak.

      This is a super highly simplistic explination of a very complex issue. There was a very wonderful -- and LONG -- 'tutorial' on memory management in Java on the sun site... but I don't have the link anymore. If someone reposts it I would be oh-so-very-happy :~)

    19. Re:problems with Java by mcc · · Score: 1
      Huh?

      I do not quite think you know what a garbage collector is. A garbage collector is generally only expected to reclaim unreferenced memory. Here, look:
      public class memoryleak { memoryleak next; public static void main(String[] args) { memoryleak head = new memoryleak(); for(memoryleak n = head;;n = n.next) { n.next = new memoryleak; } } }
      No garbage collector on earth, in any language, will be able to handle the above code. I shall leave the implementation of a similar demonstration program in LISP to the reader.
    20. Re:problems with Java by forkazoo · · Score: 1

      Well, I don't completely agree with you, but I agree that the issue is at least partly Freenet's. Freenet is made to accumulate large amounts of information over time. It caches content locally, and also known nodes. Freenet is designed to get bigger the longer it is running.

      That said, Java has no "delete." It just isn't part of the language. So, in some cases, there just isn't anything the programmer can do if the garbage collector doesn't play nice.

    21. Re:problems with Java by rbarreira · · Score: 1

      Yeah, but the programmer can do:

      ref = NULL;

      This will solve the cases where the leak is the application's fault. But it won't solve the one's which are the GC's fault (if they exist)...

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    22. Re:problems with Java by ArmorFiend · · Score: 1

      (let ((big-list nil))
      (loop (push 1 big-list)))


      Someone is confusing useful data and garbage. Either its the freenet programmers, or the GC implementors, or the slashdot java complainers. I lack the data to make the determination.

  12. Improvement from the open source community by Anonymous Coward · · Score: 0

    I get the feeling that the core of Java has been allowed to stagnate at Sun, and they've mostly been concentrating on their web applications for Java.
    Maybe once the open source community get their hands on it, they can start improving the VM and actually have it start performing at acceptable speeds.

    1. Re:Improvement from the open source community by Decaff · · Score: 1

      I get the feeling that the core of Java has been allowed to stagnate at Sun, and they've mostly been concentrating on their web applications for Java.
      Maybe once the open source community get their hands on it, they can start improving the VM and actually have it start performing at acceptable speeds.


      The real situation has been the exact opposite. The latest version of Java (5.0) was a major upgrade of core features, with significant new language extensions. The VM is now very fast, with an improved start-up time for applications, and the ability to approach C/C++ speed even for numerical work.

  13. Java is ALREADY opensource, you monkeys by bigbinc · · Score: 0, Insightful
    Java has been opensource since early on. You can see the source of almost every application in the suite through the mustang dev project.

    Get the wording right. If you mean Java might get a more open license or Apache/BSD style license say that.

    --
    ---- Berlin Brown http://www.newspiritcompany.
  14. Maybe I'm reading this wrong, but by AutopsyReport · · Score: 1, Informative
    "individuals had to sign an agreement under Sun's Java Research License (JRL), which restricts its use beyond research and development efforts and prohibits any internal implementations."

    Isn't the purpose of open-source to allow customizations through new implementations of said software?

    --

    For he today that sheds his blood with me shall be my brother.

  15. Re:Great timing... by FidelCatsro · · Score: 3, Insightful

    " As if Java isn't slow enough, they open source it just in time as .NET is 100x better and faster."
    Wow , i had no idea that .net was that much faster than natively compiled C binaries, considering Java is anywhere between 75-95% percent of the speed of C (Statistics pulled out of nowhere, i remember last time i checked Java was expected to be around 90% of the speed of Compiled C i was guessing that improved)
    That would make .net considerably faster than C ;)

    --
    The only things certain in war are Propaganda and Death. You can never be sure which is which though
  16. Open source - a cancer or not? by bogaboga · · Score: 0, Troll
    Isn't SUN the company that said OSS is a cancer in 2001? Now come 2005 and they are embracing "the CANCER?"

    I am supprised about SUN's move and wonder whether this move by SUN will also mean that it will be more open about SCO's case. SUN have been silent throughout.

    SUN should be saying these words, or these words should be going on in SUN's mind..."Life is still worth living because even as costs double and profits fade, we (SUN) still hang on!"

    1. Re:Open source - a cancer or not? by Shrapn3l · · Score: 1

      Sun won't be embracing the "cancer". What they are doing would be like Microsoft giving away the source code for programs made in Visual Basic (none of which I can recall at the moment ). All they are trying to do is gain more support for Java and its use in further applications.

      --
      That that is, is.
    2. Re:Open source - a cancer or not? by k98sven · · Score: 1

      Isn't SUN the company that said OSS is a cancer in 2001? Now come 2005 and they are embracing "the CANCER?"

      No, they didn't. They've said bad things about the GPL, for sure, but not about OSS.

      Perhaps you should recall them open-sourcing OpenOffice in 2000?

      I am supprised about SUN's move and wonder whether this move by SUN will also mean that it will be more open about SCO's case.

      What the heck does any of this have to do with the SCO case?

      Sheesh, drop the "with us or against us" attitude, will you?

  17. Too late Java is not cool anymore by expro · · Score: 4, Insightful

    This doesn't really matter to Java detractors. IT types, usually not programmers, will bring up the same old tired clichés.

    Same tired old cliches. I can tell you first hand that lots of major developers of Java and early advocates have been turned off directly by issues that could have been addressed by open sourcing it. But that won't stop you from your tired cliches that it doesn't matter, just because you don't want it to matter.

    I was developing major applications with it before it reached 1.0, and still work with it quite a bit, but it becomes more and more irrelevant despite my best work because Sun wills it to be irrelevant. Even as a major early licensee of Java, basic problems were not considered important enough for Sun to solve, and it hasn't changed much.

    Somewhere around the year 2000 Java became uncool especially with younger programmers. I guess because it became an institution taught in high schools everywhere. Maybe programmers feel Java is rammed down their throats so they champion less established languages even something by Microsoft.

    Again, strong on cliche, very weak on technical understanding or demographic fact, but at least you contradict your prior nonsense that it is not programmers turning away.

    Java really is the best thing out there for a lot of things. Sun can give away everything and detractors will be like: "OK but what about your first born child?"

    Go whine somewhere else. You think you should dictate what is useful to us without giving us adequate control to meet our needs? We will continue to use Java less and less as other tools continue come forward that are more responsive to our needs. The stuff we run today in Java doesn't benefit from the JVM and will be ported away as performance becomes more important and other features we need to build in are still not available in Java, since it is not open.

    The whole attitude that somehow open source is wanting more from Sun than it would contribute back is ignorant, uninformed, short sighted, etc. Sun and their apologists should get a clue. Open source would make it responsive to a much wider range of developers and would produce developments Sun was too blind to pursue or pursued way too late and too little. Any harm has already been done to a great extent by Sun's pig-headedness. They should go off in a corner and use it by themselves if they don't want to open it up.

    Waiting for Java has become a dead issue. No one expects Sun to get a clue, so why are you still whining that some in the past thought they might.

  18. in feeble protest.... by ChiGodOfKarma · · Score: 0, Offtopic

    Who is John Galt?

    1. Re:in feeble protest.... by ChiGodOfKarma · · Score: 0, Offtopic

      To trade by means of money is the code of the men of good will. Money rests on the axiom that every man is the owner of his mind and his effort. Money allows no power to prescribe the value of your effort except the voluntary choice of the man who is willing to trade you his effort in return. Money permits you to obtain for your goods and your labor that which they are worth to the men who buy them, but no more. Money permits no deals except those to mutual benefit by the unforced judgment of the traders. Money demands of you the recognition that men must work for their own benefit, not for their own injury, for their gain, not their loss--the recognition that they are not beasts of burden, born to carry the weight of your misery--that you must offer them values, not wounds--that the common bond among men is not the exchange of suffering, but the exchange of goods. Money demands that you sell, not your weakness to men's stupidity, but your talent to their reason; it demands that you buy, not the shoddiest they offer, but the best that your money can find. And when men live by trade--with reason, not force, as their final arbiter--it is the best product that wins, the best performance, the man of best judgment and highest ability--and the degree of a man's productiveness is the degree of his reward. This is the code of existence whose tool and symbol is money. Is this what you consider evil?

  19. Closer? by Anonymous Coward · · Score: 1, Insightful

    How many steps are there?

    1. Re:Closer? by m50d · · Score: 1
      There are two steps.

      1. Release something we've never heard of in the hope it will get people clamouring for an open Java to shut up. This can be repeated as many times as they like, and this seems to be one of those times.

      2. Actually open source the damn thing. Of course they won't actually do that until nearly everyone has given up on the language.

      --
      I am trolling
  20. Re:Won't Stop Java's Slide by Anonymous Coward · · Score: 1, Insightful

    excellent work

    +5 jibberish

    Javascript != Java
    Outsourcing has what to do with this?

  21. Sun won't see it comming by happyfrogcow · · Score: 1

    Java is dead, long live LISP.

    1. Re:Sun won't see it comming by EmperorKagato · · Score: 1

      What is LISP?

      /sarcasm

      --
      ----- You know you have ego issues when you register a domain in your name.
  22. One word by Anonymous Coward · · Score: 0

    Themes.

  23. Open source Java - so what? by squoozer · · Score: 2, Interesting

    I have been a Java developer since year dot (well it feels like it) and I can't understand the fuss about having an open source Java. Most of the libraries that I use (in fact all I think) are fully open source along with the application server the only bit that isn't is open is the core libraries but these are given away for free and I have never run into a license issue.

    The only thing that I would like in terms of openness is a packaging license that allows the registered linux distributions to repackage the JVM because current installation methods are a pain (I'm on Debian which probably makes it worse that on a lot of other distros).

    Other than that I like the stability that is granted by having one company at the wheel. If Sun decided to loose the plot and start imposing strange conditions on VM useage I am sure an open source VM would appear the day after tomorrow. Until then though I will keep buy as many free VMs as I can.

    --
    I used to have a better sig but it broke.
    1. Re:Open source Java - so what? by Anonymous Coward · · Score: 0

      If Sun decided to loose the plot and start imposing strange conditions on VM useage I am sure an open source VM would appear the day after tomorrow.

      Uhh.. no. Unless you consider "the day after tomorrow" to be 5 years from now. Writing a JVM is no small undertaking, and would take quite a while for any open source effort to produce a complete one that could replace Sun's JVM. Unless you are implying that IBM or BEA would open-source their JVM, which is questionable. But even then you need open source class libraries, not just the JVM.

      That is why we need an open source Java project (like Harmony) to start now to get things done before any possible worse-case scenario where licensing of Java goes crazy (think Sun getting bought out). Although I would prefer to see reuse of existing projects such as GNU classpath, Kaffe, etc as much as possible.

    2. Re:Open source Java - so what? by kernelpanicked · · Score: 0

      current installation methods are a pain (I'm on Debian which probably makes it worse that on a lot of other distros)

      Last time I checked all you Linux users had to do was
      # ./j2somebullshit.bin

      and set a couple PATH variables. Try being a BSD user and compiling that huge bastard yourself, then you'll know the real pain of closed source java.

      --
      Ubuntu: If at first you don't succeed, blindly slap a sudo in front of it
  24. Two words by Anonymous Coward · · Score: 0

    Unacceptable.

    1. Re:Two words by PierceLabs · · Score: 2, Funny

      Uhh, sorry but isn't "unacceptable" still just one word?

    2. Re:Two words by Anonymous Coward · · Score: 0

      not when you concatenate it with "themes."

  25. The Source Codes by Anonymous Coward · · Score: 0

    And how will the Suns opening up the source codes increase my the productivities?

  26. Write Once... by Mark_MF-WN · · Score: 2, Informative

    Thanks for not understanding anything about Java. Java CAN use native widgets -- check out SWT. SWT apps look great. Take Eclipse and Azureus for example: they're superb applications, they integrate well with nice shortcuts and launchers and whatnot, and they look wonderful. Even swing apps can look great if some effort is put into their design; Netbeans is a great IDE.

    1. Re:Write Once... by Anonymous Coward · · Score: 0

      Even swing apps can look great if some effort is put into their design; Netbeans is a great IDE.

      Presumably you've got some kind of uber-machine with 3 gigabytes of RAM and a 9 Ghz processor. I'm running an Athlon XP 2000+ with 512Mb of RAM and Netbeans reduces this machine to a crawl... literally. It's the worst IDE I've used since... I tried last version of NetBeans. It also happens to be ugly (like most Java apps), but I could live with that if it was any good. I mean really, using Netbeans is like wading through treacle.

      Incidentally, I tried eclipse too. That's also pretty slow and uses gobs of memory (it's a general feature of all Java apps)... but it's a lot faster and less memory-hungry than Netbeans.

    2. Re:Write Once... by njcoder · · Score: 2, Informative
      I use netbeans on a similar setup. Same amount of memory and a comparable processor. I don't have a problem with it being slow. I want to get more memory because running netbeans and the appserver takes up a lot of memory which means I can't run a lot of other applications at the same time. Have the same problems with eclipse. Eclipse seems to start up with less memory but doesn't take long to catch up.

      The only really uggly thing I see in NetBeans is the properties editor window. I like the way it looks in the windows native look and feel. The new metal look and feel I think takes up a little bit more memory but in my opinion looks even nicer.

      If you're not using Java 1.5 try it, it speeds NetBeans up a bit. Also I shut down a lot of other apps/tools when I run netbeans to free up memory. Have to do this for other non Java applications I'll be working with for a long period of time as well. Try freeing up as much memory as you can then try NetBeans. It might be worth the price of an extra stick of memory.

    3. Re:Write Once... by Anonymous Coward · · Score: 0

      I use netbeans on a similar setup. Same amount of memory and a comparable processor. I don't have a problem with it being slow.

      I can only interpret that as meaning "I don't mind it being slow".

      Otherwise, I can only assume that you are simply lying or insane. I've tried NetBeans on seven (7) different machines in configurations ranging from 1Ghz (256Mb) to this 2000+ (512Mb) Athlon... they were *all* slow enough to completely unusable. Oh, and I am running the latest version of Java supplied by Sun:

      java version "1.5.0_03" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_03-b07) Java HotSpot(TM) Client VM (build 1.5.0_03-b07, mixed mode, sharing)

      NetBeans is the slowest and most memory hungry application I've seen. I (among other developers) was asked to evaluate it for use... every single one of us turned our noses up in what can only be described as disgust at just how bad it was. Eclipse got a "passable but moderately horrid" grade.

    4. Re:Write Once... by njcoder · · Score: 1
      "I can only interpret that as meaning "I don't mind it being slow"."

      There are other interpretations of that as well. I don't find it slow. I type pretty fast (80-90wpm) and I don't have to worry about it being slow. It starts up less than 40 seconds which I think is pretty good for an application as big as NetBeans. Windows open up and redraw fast. Menus don't seem any slower than native apps. The classpath scanning it does when you first load it is annoying but I've seen the 4.2 q-builds and it looks like they took care of that by making it a background process.

      Is it slower than something like textpad? Yeah, but so is any other IDE with as many features in my experience. Is it so slow that it I notice difference? No. I find lynx faster than FireFox but that doesn't make me use it more. If I need to quickly check my email from someone else's computer I'll sometimes just telnet into the pop3 server because it's a lot faster, but that's not my primary email checking method. As long as it's not starting to swap and stays mainly in real memory it runs great in my experience. Like I said, I shut down stuff I won't be using when I run it, like Outlook and at least one IM client but I still can keep PostgreSQL running as well as PGAdmin and a data modelling app as well as FireFox. This is in addition to NetBeans and Tomcat.

      If I open up photoshop and start working on a bunch of images I'll have a problem with waiting for things to come out of swap but then it runs fine after that. So I just seperate my workflow and work on graphics and code seperately. The IDE makes me more productive, and making me shutdown email and im makes me even more so :) If only I had to shut off my phone :)

      Before starting NetBeans, after shutting everything I usually shutdown down, I run MaxMem from AnalogX to swap out whatever isn't necessary. I used to use it on a PIII with 384Megs of Ram. That was brutal. 512Megs should be the minimum if you're going to be runing netbeans, tomcat, cvs server and a database and you want to keep a browser open. I should get some more memory but it hasn't been a priority for me. I've gone through the options and turned off a couple of modules I don't need which gives me a plenty of headroom so I don't have to worry about swapping.

      I'm curious though, what is it specifically that you found slow? What type of applications are you trying to develop? What are you using instead of NetBeans/Eclipse?

    5. Re:Write Once... by Bill+Dog · · Score: 1

      It starts up less than 40 seconds which I think is pretty good for an application as big as NetBeans.

      ?!?!?!

      That zero's a typo and shouldn't be there, right? (Tell me you good Java folk aren't that insane!)

      --
      Attention zealots and haters: 00100 00100
    6. Re:Write Once... by crazyphilman · · Score: 1

      No, he's dead serious. When you start up Netbeans, you sit looking at a pretty blue splash screen. It takes about the same amount of time for Netbeans to load as for KDE to load when you first start X Windows.

      Once it's running, it's not bad, though. But, the code completion feature (you start typing, you hit ".", and a list of possible class members pops up) takes a few seconds sometimes.

      Oh, and yeah, it's a major memory hog. You should have at least around 396MB ram for it to run well.

      --
      Farewell! It's been a fine buncha years!
  27. Speling by Anonymous Coward · · Score: 0

    Steve O'Grady, an analyst at research firm RedMonk, said although the Linux community will not be happy about another open source project that isn't offered under the Generel Public License (define), he said the addition of an application server under CDDL will please organizations that have plans to use OpenSolaris.

    Indeed! For one, I've never heard of it.

  28. Re:Great timing... by rbarreira · · Score: 1

    For what kind of applications? If you are talking about pure speed, java is certainly not even 75% as fast as C... If you want to compete with some algorithm let me know - I'll do the C implementation and you'll do the java implementation, and then we'll see the difference...

    Nevertheless, that was a good reply to a troll :)

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  29. Reread the parent by expro · · Score: 1
    The parent said when all they download is a .class file?

    May as well download IBM's JVM or Microsoft's to get reasonable native widgets. With Sun's campaign against native libraries, they should have supplied something themselves and not killed off all the competing libraries, each of which worked better than theirs.

  30. Sun still doesn't get it. by oneandoneis2 · · Score: 1, Informative
    Sun officials believe that by making the source codes open to developers

    Sun still doesn't "get" open source. Check out this interview on news.com with Scott McNealy, Sun's CEO.

    We have a strategy that's very different from everybody else's, and it's community development. The way we say that is with the S curve in all our new literature. It's not for Scott, it's not for Sun, it's for "share." We're grabbing that word and saying, of anybody, we own the word "share." We own that space.

    The oxymoron appears to have gone unnoticed. But it makes it very clear that Sun is still all about proprietary stuff. They might share it, but they still own it. And that's straight from the horse's mouth.

    --
    So.. it has come to this
    1. Re:Sun still doesn't get it. by Anonymous Coward · · Score: 0

      He's using "own" in the sense of "0wn3d!", not as in literal property.

  31. Re:Great timing... by EraserMouseMan · · Score: 1

    Yea I'd like to see where you pulled those stats from. I was on a JSP development team for 2 years. We were developing web apps in Visual Age and I've used several other apps written in Java during that time. I can tell you from experience that Java apps do tend to be slower than apps not based on Java. That's just my experience with real Java apps.

    I suppose there could be some things that you could get Java to do faster than the alternatives (.NET, etc.). But when it comes down to a real application with a GUI, etc. it is definately slooooooooow.

  32. Re:Great timing... by Tony+Hoyle · · Score: 1

    .net is dog slow. Unless they've improved the performance a *lot* for 2.0 even Java could leave it in the dust.

    Comparing that to a native C implemenation is just stupid.

  33. Three words by Anonymous Coward · · Score: 0

    Oracle Universal Installer

    Iiieeeee! The tenticals!

  34. Its not exactly new by cpn2000 · · Score: 2, Informative
    No one uses Sun's app server cause its new and immature

    The product name is new, the product core is not. Other names it went by include (in chronological order)

    • iPlanet Application Server
    • Netscape Application Server
    • Kiva Application Server
    --
    All you touch and all you see is all your life will ever be ... Dark side of the moon
  35. half pregnant? by ubiquitin · · Score: 1

    Being kind of open-source is like being kind of pregnant.

    Look, either we can see the source for Java or not.

    In this case, it's a not.

    Sun: Thank you, come again.

    --
    http://tinyurl.com/4ny52
    1. Re:half pregnant? by -brazil- · · Score: 1

      Bullshit. We can see the source just, fine. All of it. The API library source comes with every JDK, and you can get the JVM source as well.

      However, the license does not allow you to change that source and distribute the changed version. That's what Open Source purists are criticizing, no the lack of the actual source code.

      --

      The illegal we do immediately. The unconstitutional takes a little longer.
      --Henry Kissinger

    2. Re:half pregnant? by LDoggg_ · · Score: 1

      Being kind of open-source is like being kind of pregnant.

      No. That analogy does not work at all.
      Lets say sun open sourced 90% of its APIs under a license that everyone loves. That would help projects like GCJ and gnuclasspath quite a bit.
      Java isn't one giant self contained executable that we need the source code to.
      There are plenty of parts that would be helpful.

      --

      "If they have both, tell them we use Linux. And if they have that, tell them the computers are down." -Dave Chapelle
  36. !SWT.equals(Java) by mcc · · Score: 2, Informative

    SWT runs on Java the language but it is not Java itself. That is to say, it is not part of the Java platform. It is a product of IBM-- it's a third party library-- and is not promoted or supported by Sun. If he wants to complain about the Java language maybe he's being unreasonable, but if he wants to complain about Sun's Java then things are quite different.

  37. Apache License would have been sweet by HighOrbit · · Score: 1

    It would have been nice if the Sun Java App Server could have become an Apache project instead of a CDDL project. It would have been a perfect match for Apache. But maybe that was asking for too much. Sun was very generous when they donated Tomcat to Apache back 1999 (and perhaps Sun's management thinks they were too generous since Tomcat forms the foundation for some products which now compete with Sun)

    Yes, I know that Geronimo is working under Apache to do an app server too, but they are still have a long way to go to be production ready.

    Note to those who become involved with the new GlassFish project. If you ever get any leverage with Sun, please ask for an Apache License.

  38. What is the "Source" Language? by mosel-saar-ruwer · · Score: 1

    This is not a step towards opening Java. The only relation this has to Java is the fact that it runs Java code and is written in Java. Just because sun open sourced it doesn't mean its thinking about open sourcing the Java lanugage.

    Okay, that would explain a lot.

    But when I first saw the thread, I thought it meant that Sun was opening the "source" to javac and java, and then I got to wondering: Okay, what language are those programs written in? C++? C? Bison?

    Or is it largely "machine code"?

    1. Re:What is the "Source" Language? by CyricZ · · Score: 1

      Sun's Java compiler (javac) is supposedly written in Java. The java program is just a front end to the Java virtual machine, which is rumored to be written in C. Bison is a technology for implementing parsers. It is not really a general programming language itself.

      --
      Cyric Zndovzny at your service.
  39. Re:Great timing... by Anonymous Coward · · Score: 0

    Which I think was point of the grandparent post

  40. What are you smoking? by Anonymous Coward · · Score: 0

    This is a free software license which is not a strong copyleft; it has some complex restrictions that make it incompatible with the GNU GPL. That is, a module covered by the GPL and a module covered by the CDDL cannot legally be linked together. We urge you not to use the CDDL for this reason.

    Also unfortunate in the CDDL is its use of the term "intellectual property".

    1. Re:What are you smoking? by snorklewacker · · Score: 1

      Show me one single license that IS compatible with the GPL, where "compatible" doesn't mean "relicensed under the GPL".

      Additionally, the GPL is based on copyright, which is an "intellectual property" mechanism. I bet I could find plenty of "unfortunate" terms in the GPL to pick on as well.

      Maybe the problem doesn't lie with all the other licenses.

      --
      I am no longer wasting my time with slashdot
    2. Re:What are you smoking? by MartinG · · Score: 1

      Show me one single license that IS compatible with the GPL

      GPL Compatible licences:

      GNU GPL
      GNU LGPL
      X11 License
      W3C Software Notice and License
      Berkeley Database License
      Clarified Artistic License
      Intel Open Source License
      Modified BSD license
      MIT License

      There are many others also.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    3. Re:What are you smoking? by Paul+Jakma · · Score: 1

      All of those are essentially BSD/MIT style licences, no?

      Got any examples of actual substantive licences which do more than, essentially, "Retain copyright, credits please" which are GPL compatible?

      --
      I use Friend/Foe + mod-point modifiers as a karma/reputation system.
    4. Re:What are you smoking? by PastaLover · · Score: 1

      Don't think you're going to find one but the FSF definition is very narrow as it is. Compatible in there book means relicensed under GPL. However, many people still argue that linking against a certain library, whether it is statically or dynamically doesn't, is allowed from any program that is not a direct extension of that library. (eg a wrapper around libssl)

      The problem off course being in the interpretation of the GPL. I think we'll only know for sure once the GPL gets tested in court.

    5. Re:What are you smoking? by snorklewacker · · Score: 1

      Of those licenses, show me which ones do not simply become the GPL when mixed with the GPL. The GPL's definition of "compatible" is "able to be relicensed perpetually under the GPL".

      --
      I am no longer wasting my time with slashdot
    6. Re:What are you smoking? by MartinG · · Score: 1

      Ah. I understand your point now and I agree with you.

      That would be the definition of compatible for just about any license though, wouldn't it?

      Personally, I don't see it as a big problem that the GNU GPL uses "compatible" to mean "can be relicensed as GPL"

      When you have various bits of code under various different licenses then either you can't mix the code because of license conflicts or it ends up being licensed under the most restrictive one. In this case the most restrictive is the GPL because it restricts the right to remove other peoples freedom. That's not too much of a problem for a license designed to protect freedom.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    7. Re:What are you smoking? by MartinG · · Score: 1

      Got any examples of actual substantive licences which do more than, essentially, "Retain copyright, credits please" which are GPL compatible?

      No. For any licence (licence A) to be compatible with My Favorite License (licence B) then license A cannot include any restrictions that are not also included in licence B. (unless I have missed something obvious)

      In the GPL example that means no compatible license can have greater restrictions. That is quite hard to find since the GPL hardly has any restrictions to start with.

      Incidentally, AFAIK "retain copyright, credits please" would be GPL compatible because "credits please" is a restriction that the GPL requires not to be imposed.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    8. Re:What are you smoking? by snorklewacker · · Score: 1

      That would be the definition of compatible for just about any license though, wouldn't it?

      You certainly can't merge two licenses together and produce a hybrid, no. At least not without negotiating with the original licensor. However, licenses like the LGPL have fairly specific exemptions, limiting their protections to the actual code being licensed. RMS has time and again shown his contempt for this "Lesser" license, but he's at least been pragmatic enough to not withdraw it from the GNU license choices.

      Cygwin is another example, with a modified GPL that won't cause relicensing of any open source license. Essentially, you can't link proprietary software to it, but it won't relicense other open source software. Of course, the idea that the GPL can somehow "taint" another program such that the author unwittingly ends up relicensing all his work to the GPL is actually a bit ridiculous -- the GPL simply can't assert rights over someone else's work. However, since you have no rights distribute the GPL'd code any other way, distributing it and leaving it that way for years could be considered tacit agreement to the terms of the GPL. And most authors simply take the path of least resistance and choose GPL for that reason.

      So while the GPL technically isn't so virulent a virus as some would have it, it still tends that way. And this is probably just the way RMS wants it. It may have been necessary back in the days of 100% proprietary platforms, or even the old shareware days when software was becoming "free", but with obnoxious strings attached. The culture had to be shifted toward completely free, and building a software culture around a single license was a means to that end. I'm not so sure it's the best fit to modern times, but then again, each new platform has brought a resurgence of both proprietary lock-ins and annoying crappy shareware, so there's cause for the FSF to dig in its heels to this day.

      --
      I am no longer wasting my time with slashdot
    9. Re:What are you smoking? by civilizedINTENSITY · · Score: 1

      I prefer to call it an inoculation rather than a virus. I think inoculation fits the intent of, and as far as I can see, the effect of, the GPL quite well.

  41. Re:Java is dying. by sproketboy · · Score: 3, Interesting
  42. Re:Great timing... by -brazil- · · Score: 1

    If you are talking about pure speed, java is certainly not even 75% as fast as C

    Yes, it most certainly is. However, it does tend to be a bit of a memory hog, which slows down larger apps. Then again, big fat C++ apps like OpenOffice aren't exactly blinding fast either.

    --

    The illegal we do immediately. The unconstitutional takes a little longer.
    --Henry Kissinger

  43. plug plug by ChristTrekker · · Score: 1
    If they don't, they run tomcat (if no EJBs requried) or JBoss.

    Or JOnAS!

  44. Re:Great timing... by rbarreira · · Score: 1

    Those benchmarks seem like crap to me - the first four are supposed to be more or less equal for C and a Java JIT compiler, since from what I can see, they're just coding C in java (ie, no objects, just loops with variables of primitive types, etc).

    The I/O benchmark is just ridiculous, since it's... I/O bound by definition. It just proves that most of those languages are not the bottleneck when doing I/O :)

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  45. Java is not slow . Does use memory by zymano · · Score: 1

    Java is a COMPILER and an interpretor. The startup time plus compiling causes confusion even to computer experts. Too many people that I trust say its fast once it gets going.The only negative is that it's both a compiler and an interpretor and is trying to do too much.Sun maybe should have kept java just an interpretor like PYTHON and PEARL and then people might not complain about speed.

    Another idea would have been to have it 'COMPILE' code into native just like a c compiler.

  46. Eclipse relies on non-Sun native libraries SWT. by expro · · Score: 1

    You made the case for the opposition. Now cite a product that runs in pure Sun Java and can be redistributed as a simple class library. Anyone can make a native entry point allowing better native implementations to be invoked by Java, but then most of what is claimed about Sun Java becomes false.

    1. Re:Eclipse relies on non-Sun native libraries SWT. by tolkienfan · · Score: 2, Informative
      SWT exists because AWT and Swing didn't meet the needs of the project.
      If Sun had been sensible with Swing, it could have produced something responsive and useful like SWT.
      IF SWT were part of the Java runtime, would you make the same point?

      All GUI features have to hook into the OSes graphics library at some point - making them native.
      Third party native hooks versus built-in hooks - a bit of a fine line there. Especially since SWT runs on most platforms, and platforms that aren't supported could be ported since SWT is OSS.

    2. Re:Eclipse relies on non-Sun native libraries SWT. by expro · · Score: 1

      SWT exists because AWT and Swing didn't meet the needs of the project. If Sun had been sensible with Swing, it could have produced >something responsive and useful like SWT.

      Exactly. More particularly, if Java were open, SWT or something better would ship with most JVMs.

      IF SWT were part of the Java runtime, would you make the same point?

      Let''s see... If Java didn't generally suck as shipped and limited by Sun, would I make the same point that it sucked as a result of no one who cared about improving it being empowered to do so? Probably not.

      All GUI features have to hook into the OSes graphics library at some point - making them native. Third party native hooks versus built-in hooks - a bit of a fine line there. Especially since SWT runs on most platforms, and platforms that aren't supported could be ported since SWT is OSS.

      Exactly the point. Sun implementations suck, Even limited OSS replacements available for parts such as the UI suck less. The more open Sun were to more OSS improvements that could be shipped with significant JVMs, the less it would suck. While IBM can ship this sort of modification with a JVM, even they are restricted and most potential contributors could not because, again, it is not open and Sun goes to great lengths to keep it closed.

    3. Re:Eclipse relies on non-Sun native libraries SWT. by Decaff · · Score: 1

      While IBM can ship this sort of modification with a JVM, even they are restricted and most potential contributors could not because, again, it is not open and Sun goes to great lengths to keep it closed.

      SWT is nothing to do with the open-ness of Java. SWT is not a mondification. It is a set of open source Java classes and C code that provides link to the underlying API. There is no restriction on them shipping this along with JREs, and there is no restriction on anyone else shipping additional libraries.

    4. Re:Eclipse relies on non-Sun native libraries SWT. by tolkienfan · · Score: 1
      I think the point was that since Java is not open source, you can't get something like SWT into the base tree (without Sun's JCP process) - which would undoubtedly be useful.

      SWT is not a modification per se, but it does offer a replacement for AWT or Swing; however, since it does not form part of the JVM and it uses native code, programmers can't rely on it being available, as they can for other APIs.

      The native code part is key, because it means you can't ship the SWT library with the app. And you can't assume it's already there.

      Acutally you can, but:

      1. You have to ship a version for each supported platform
      2. You can only support platforms to which the library has been ported

      If Java were open source, SWT could be incorperated, and become a standard API supported on every platform that Java runs on.

    5. Re:Eclipse relies on non-Sun native libraries SWT. by Decaff · · Score: 1

      If Java were open source, SWT could be incorperated, and become a standard API supported on every platform that Java runs on.

      This could be a negative step. Not everyone wants SWT. There is increasing pressure for the JRE to be reduced in size and made more modular.

    6. Re:Eclipse relies on non-Sun native libraries SWT. by tolkienfan · · Score: 1
      Not everyone wants Swing.

      That's not much of an argument against open sourcing Java.

    7. Re:Eclipse relies on non-Sun native libraries SWT. by Decaff · · Score: 1

      Not everyone wants Swing.

      That's not much of an argument against open sourcing Java.


      It is. The argument being put forward was that open sourceing was necessary so that additional features could be added into the standard distribution. If the standard distribution is to be cut back with lots of features being optional and separately downloaded modules, then there is nothing to stop open source extras being downloaded as such modules.

  47. Re:Java is dying. by kryptx · · Score: 2, Interesting
    This list is a prime example of the types of non-sequiturs and half-truths that people will conjure up to try to bash corporations for the sake of bashing corporations. The fact that it's been modded 'Informative' is disappointing. Few of the items on that list are legitimate issues. Many of them are simply differences in the relative maturities of the languages. Some are misunderstandings about the way the languages were intended to work. Others are outright lies. The last one is self-referencing and redundant. I urge readers to comb through it before accepting it as justification for their corporate hatred.

    The fact of the matter here is that .NET brings many of the benefits of Java to the fingertips of developers without the slow runtime environment. But for the sake of being thorough, let's list the real problems with .NET.

    • Poor documentation. This is a huge issue even in the .NET community. The best documents there are for .NET are the comments on the prototypes in the SDK. That is unacceptable.

    • Portability. This is obviously motivated by profits, which is understandable, but still a drawback for the software community at large. In that light, Microsoft should have released the platform for linux and OSX. The related open-source projects are changing this, but they should never have been necessary.

    • Exception handling. It's there, it's decent, but it's not quite as good as Java.

    I'm sure there are projects that are better suited to be written in Java. But the software community, if they want to save Java, will eventually be forced to "respond" to .NET. Because there are more people who care about how fast their program does what they expect it to do than there are who care whether their platform is owned by Microsoft. I anticipate there will be a shift towards native compilation. Whether it will work depends on how soon they do it.
    --
    Mods: Do you disagree with me? Go ahead and mod me down. Meta-mods will sort it out. Good luck!
  48. Re:Java is not slow . Does use memory by smackjer · · Score: 1
    Another idea would have been to have it 'COMPILE' code into native just like a c compiler.

    But then it wouldn't be "write once, run everywhere". That's one of Java's main selling points.

    --

    This is my sig. There are many like it, but this one is mine.
  49. Re:Java is not slow . Does use memory by stelmach · · Score: 1

    Another idea would have been to have it 'COMPILE' code into native just like a c compiler.

    The JVM does convert the byte code into native machine code. All programs need to be converted to native machine code in order to run.

    Sun maybe should have kept java just an interpretor like PYTHON and PEARL and then people might not complain about speed.

    I'm quite certain that the speed would be much worse if the JVM simply interpreted the byte code rather than compiling it. It seems that you are a bit confused about the difference between an interpreter and a compiler. An interpreter will run through all of the steps of a compiler on the fly, but will not store the results of the parse tree, type checking, etc. This means that an identical piece of code that is executed 1000 times in an interpreted language will be re-parsed and re-type checked 1000 times. Java is a bit smarter than that. It will do the compilation on the fly, AND store the results for the next time it is needed. (Which is why some java programs seem to require more an more memory as they are executed.)

    What I think would make a lot of people happy is if Sun released a more tradional compiler. Such compilers do exist (like GCJ for example,) but they do not support all of the Java libraries (As far as I know, Swing is not supported in any of these compilers.) I guess this would break the write once, run anywhere view that Sun has had for the past ten years, but I think we all know that that will never be truly achieved.

  50. Open Source means attractive deployment options by aCapitalist · · Score: 1

    FortKnox seemed to clear up the confusion about "Sun closer to opening up Java", but on a more general note - I would find Java to be a much more attractive desktop solution if I could compile Java down to an .exe.

    Yes, I know about GCJ, but that only works with a subset of current java (that I'm aware of) and I think even commercial native compilers like Excelsior Jet (or something like that) can't compile Swing apps.

    I don't care about the politics of open sourcing it, but open sourcing java just gives me many more options when considering something that isn't server side.

    But Sun still has this fear of opening up under the same excuse of "our corporate customers don't want incompatible forks". It's Sun's baby and all, but how much do they even make on Java? And will they ever recoup the development costs?

    1. Re:Open Source means attractive deployment options by StarsAreAlsoFire · · Score: 1

      Not joining the pitched battle, just wanted to say that Borlands JBuilder will compile swing apps. I tend not to use it out of paranoia -- Why introduce the possibility of errors, esp. when I have no desire to add the additional testing to the mix?

      But I have tried it for small apps, and never had a problem. Again *NOT A HEAVY USER*.

    2. Re:Open Source means attractive deployment options by NeoBeans · · Score: 1
      FortKnox seemed to clear up the confusion about "Sun closer to opening up Java", but on a more general note - I would find Java to be a much more attractive desktop solution if I could compile Java down to an .exe.

      Let's set the wayback machine for 1995...

      Java became popular because it was a lightweight programming langauge that allowed developers to create applications that could run on a variety of platforms.

      That wasn't going to happen if the binaries were Windows executables...

      The importance of the Java bytecode format for distributing binaries was a huge reason that Java was able to capture mindshare. Without that, it would have been "just a programming language" and not a new platform for developers.

  51. Re:Great timing... by -brazil- · · Score: 1

    Those benchmarks seem like crap to me - the first four are supposed to be more or less equal for C and a Java JIT compiler, since from what I can see, they're just coding C in java (ie, no objects, just loops with variables of primitive types, etc).

    So what you're saying is that you want to benchmark not languages but programming paradigms?
    Or just rig the benchmark so that it might support your false original claim?

    --

    The illegal we do immediately. The unconstitutional takes a little longer.
    --Henry Kissinger

  52. Re:Great timing... by rbarreira · · Score: 1

    I'm saying that for a typical moderately complex program made in both languages C will be faster than Java. Just as the same program made in C and C++ will tipically be slightly faster in C, but the code is also stightly more difficult to understand in some types of applications. Of course, if you're going to do "inline asm" in C and C++, the performance will be the same...

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  53. no closer to open source by a137035 · · Score: 2
    It doesn't matter how many million lines of Java code Sun open sources as long as they still own the platform, and they do still own the platform:
    • Sun is the final arbiter of what constitutes a Java-compliant application. People incorrectly claim that Sun's control extends only over the trademark, but that's not true: they can keep you from shipping your Java implementation through patents and the licenses on their specifications if they don't like what you are doing, no matter what you call your Java.
    • The Java specifications that you need to create your own Java implementation are only available under a strict license (the fact that you can download them so easily from java.sun.com makes it even worse)
    • Sun owns several patents on key technologies needed for creating a compliant Java implementation
    • The only Java implementations actually capable of running the code are Sun's and licensed derivatives.
    Maybe the creation of a fully open source Java implementation by IBM, Apache, and/or GNU will finally force Sun's hand--while technically, non-enforcements of their patents and licenses against such open source projects doesn't invalidate their claims, practically, they would have to act or face tough questions. But until the legal status of open source Java implementations is resolved (or Sun abandons their ridiculous patent and license claims), the only Java there is is proprietary: Sun Java and its derivatives.

    And open sourcing stuff built on top of their proprietary platform doesn't bring it one step closer to open source. Quite to the contrary: it merely looks like an attempt to drum up business for their proprietary platform.

  54. Re:Java is not slow . Does use memory by zymano · · Score: 1

    Java compiles to bytecode which is 'not' native. The bytecode is for the java processor(virtual machine).

    Python and Perl seem fast on startup because they don't have to compile to bytecode.

    Native code is what c or c++ compilers create.

    http://www-106.ibm.com/developerworks/java/library /j-native.html?loc=j

    Your other point about GCJ is what I was saying.

  55. in other words... by namekuseijin · · Score: 1

    open and free ( as in beer ), but with no freedom for developers to modify it to suit their needs and redistribute that.

    open sources sure does not mean freedom as the free software movement tries hard.

    --
    I don't feel like it...
  56. Re:Java is not slow . Does use memory by stelmach · · Score: 1

    When you compile your java code into a .class file using javac, this is producing byte code. The byte code is then run on a JVM that will further compile the byte code into machine code. Let me re-iterate, NOTHING other than machine code can ultimately run on a CPU. There is no java byte code engine built into the processor. Python and Perl are fast on startup because they simply traverse the parse tree and generate machine code as they go. They do not need to worry about storing the results of the parse tree.

  57. James - Is That You? by Anonymous Coward · · Score: 0

    No one else could type that and control their laughing long enough to click "submit".

    1. Re:James - Is That You? by Decaff · · Score: 1

      No one else could type that and control their laughing long enough to click "submit".

      Nothing like reasoned argument is there?

      Java's portability is a plain fact. Major complex applications such as JBoss run on Windows, Linux, MacOS.. and all other J2SE platforms with no changes. The quality of the Linux implementations is demonstrated by it's use on that platform by high-performance sites such as E-Bay.

      So given the choice between the opinions of one AC and the opinions of developers in major financial institutions and in some of the most successful websites, I know which I would listen to.

    2. Re:James - Is That You? by Anonymous Coward · · Score: 0

      Did you read the message? I've just done it and it specifically talked about "DESKTOP APPS." I whole heartedly concur with the post to which you replied: java sucks for desktop work. Swing blows -- particularly under Linux -- Sun just doesn't give a shit about Linux, doubly so these days with "Open"Solaris.

    3. Re:James - Is That You? by Decaff · · Score: 1

      Did you read the message? I've just done it and it specifically talked about "DESKTOP APPS."

      No it didn't. Let me quote:

      "Java is a corporate quagmire and on Linux it is seriously shite."

      I whole heartedly concur with the post to which you replied: java sucks for desktop work. Swing blows -- particularly under Linux -- Sun just doesn't give a shit about Linux, doubly so these days with "Open"Solaris.

      Nonsense. Sun sells Linux systems. They have major development teams producting software for it (such as the JVM). A very strange way of 'not giving a shit'!

      As for Swing, it is now one of the standard ways to develop on MacOS/X, and a Swing-based development tool - NetBeans - won the 'Open Source developer tool 2005' award from developer.com - a site that deals with far more than Java. Sure looks like the 'Swing blows' statement might be mistaken?

    4. Re:James - Is That You? by Mock · · Score: 1

      Beyond that, there's nothing stopping people from developing using SWT if they don't like swing.
      It's not as flexible, but it's MUCH faster.

      Have a look at what it can do:

      http://sancho-gui.sourceforge.net/images/ss-new-1. png

      They even have natively compiled binaries for it!

      And let's not forget the guys who invented swt:

      http://www.eclipse.org/

      Of course, that's not to say that swing sucks:

      http://www.powerfolder.com/8603/39627.html

      Mmm. nice isn't it? I certainly wouldn't spot this a mile away as being swing.
      That is what we call an example of a programmer doing his job right.

      I used to hate swing applications too, but that was when I ran a 500MHz machine. CPUs are cheap these days.

    5. Re:James - Is That You? by Anonymous Coward · · Score: 0

      No it didn't. Let me quote:

      You take one sentence out of context and ignore everything else. Just how much of a liar are you?

      Let me quote the final paragraph: The fact that you can claim Java is in *any* way a serious system for cross-platform desktop development betrays a complete and total break with reality. You might try using it in the real world.

      This is in addition to the fact that the post repeatedly talks about Swing.

      Nonsense. Sun sells Linux systems. They have major development teams producting software for it (such as the JVM). A very strange way of 'not giving a shit'!

      Bullshit. Sun *sold* Linux systems. What's the next version of JDS going to be based on? Linux is about as low-priority as you can get at Sun, and still be considered as "supported".

      As for Swing, it is now one of the standard ways to develop on MacOS/X, and a Swing-based development tool - NetBeans - won the 'Open Source developer tool 2005' award from developer.com - a site that deals with far more than Java. Sure looks like the 'Swing blows' statement might be mistaken?

      I couldn't give a flying crap about bought awards. I've used NetBeans... and it was awful (eclipse was slightly better). As for Mac OSX, that's a case study in desperation -- and "one of the standard ways of developing" is just about as vague and meaningless as you can get. Writing apps in Perl is "one of the standard ways of developing OSX apps." Could you perhaps name some prominent Mac OSX apps that are developed with Swing? No sneaky listing Sun dev tools or obscure shareware apps either.

    6. Re:James - Is That You? by Decaff · · Score: 1

      You take one sentence out of context and ignore everything else. Just how much of a liar are you?

      The sentence stood alone. Let's look at another sentence from that post:

      "Sun's entire Java package for Linux sucks..."

      Nothing specific about desktop java there. Quite the opposite.

      Bullshit. Sun *sold* Linux systems.

      Why post this when a simple check on Sun's website proves you wrong?

      Sun ships Linux *now*.

      What's the next version of JDS going to be based on?

      From Sun's website:

      "Initially provided with a Linux OS, Java Desktop System is now also integrated with the Solaris 10 Operating System."

      Also, not instead of. They are broading the range of OSes on which you can get JDS, not changing it.

      The JDS Q & A:

      "Future versions will extend platform support to the Solaris SPARC and x86 platforms."
      Linux is about as low-priority as you can get at Sun, and still be considered as "supported".

      Nonsense. The JVM on Linux is kept just as up-to that on other platforms. Sun also provides Star Office for Linux, their app server for Linux, their Enterprise System for Linux ...

    7. Re:James - Is That You? by Decaff · · Score: 1

      I couldn't give a flying crap about bought awards.

      It wasn't a bought award. I assume you have evidence to back up this accusation?

      Could you perhaps name some prominent Mac OSX apps that are developed with Swing? No sneaky listing Sun dev tools or obscure shareware apps either.

      NeoOffice/J for Mac - just released.

    8. Re:James - Is That You? by Anonymous Coward · · Score: 0

      NeoOffice/J for Mac - just released.

      I believe he asked for "prominent Mac OSX apps that are developed with Swing". 1. NeoOffice isn't a Swing app, or a least the vast majority of its interface isn't Swing. 2. NeoOffice isn't prominent, it's just a small fork of OpenOffice. That was pretty desperate dude...

      You fail it!

    9. Re:James - Is That You? by Decaff · · Score: 1

      I believe he asked for "prominent Mac OSX apps that are developed with Swing". 1. NeoOffice isn't a Swing app, or a least the vast majority of its interface isn't Swing. 2. NeoOffice isn't prominent, it's just a small fork of OpenOffice. That was pretty desperate dude...

      You fail it!


      Yes, I did. With good reason. There aren't prominent Mac OSX apps developed with Swing. Almost no-one writes Java specifically for MacOSX, or Linux, or Windows. They write portable Java applications, which are able to run on those platforms.

      There may be good reason to target MacOSX with Java, but in principle, it is Java used wrongly. What Apple provides is a very-high quality implementation of Swing that allows general portable Java applications to look like Aqua when running on MacOSX.

      Asking for Java applications that target MacOSX is as silly as to ask for PERL or Python applications that target Pentium chips.

      I was naive to have fallen into the trap!

  58. Cross-platform & Open Office success by Xoo · · Score: 1

    I'm no programmer, however isn't Java's appeal the fact that it's very easy to make Java apps cross-platform?

    While Sun's intentions in open sourcing their products may not be neccesarily benign, they ARE giving *something significant* to the open source communuity. The best example I can give is OpenOffice.

    Sun does have it's own commercial office suite called StarOffice which is derived from the OO suite, however OO is being developed into a very well-rounded competitor.

    NeoOffice/J for OS X is a great opensource alternative for MS Office, and that project has its roots in the OpenOffice suite.

    --
    Karma police, arrest this man, he talks in maths....
    1. Re:Cross-platform & Open Office success by a137035 · · Score: 1

      While Sun's intentions in open sourcing their products may not be neccesarily benign, they ARE giving *something significant* to the open source communuity. The best example I can give is OpenOffice. OpenOffice is great, and it's nice that Sun has open sourced it. However, "don't worry about Java being proprietary because OpenOffice is open source" is not much of an argument. I'm no programmer, however isn't Java's appeal the fact that it's very easy to make Java apps cross-platform? For some definition of "easy" and "cross-platform". One big problem is that, in the end, Sun decides which platforms Java gets implemented on, and some platforms are just out of luck.

  59. Re:Java is not slow . Does use memory by Bill+Dog · · Score: 1

    First of all, you don't compile your java code into a class file, you "compile" it. In Computer Science compilation produces machine code. javac does not.

    Secondly, to your post two levels up, I don't think merely adding caching to an interpreter suddenly makes it not an interpreter. I'm sure MS's classic VB runtime cached things in loops at least. And it was definitely an interpreted language (it did eventually allow the option of making an EXE, but I don't know if it actually compiled the p-code or whatever to machine code, or just linked in the VB runtime).

    Which brings me to what I'm wondering about: You say the JVM compiles the byte code into machine code. I seriously doubt that that's true. Does the JVM really take your byte code and build an executable and spawn a process for it? Until I hear otherwise, I'm under the assumption that it does not, that rather the JVM is compiled, and that your byte code never is, but is interpreted (and cached) by the JVM. That is, only JVM code is ever machine code. Please correct me if I'm wrong.

    --
    Attention zealots and haters: 00100 00100
  60. Re:Great timing... by Decaff · · Score: 1

    For what kind of applications? If you are talking about pure speed, java is certainly not even 75% as fast as C...

    Yes it is.

    If you want to compete with some algorithm let me know - I'll do the C implementation and you'll do the java implementation, and then we'll see the difference...

    This page includes results for a well-established benchmark for math processing - Linpack.

    http://www.shudo.net/jit/perf/

    It shows Sun's JDK 5.0 being more than 90% of the speed of C/C++.

  61. Re:Java is not slow . Does use memory by downbad · · Score: 1
    All programs need to be converted to native machine code in order to run.
    Surely you jest.
  62. Re:Java is not slow . Does use memory by stelmach · · Score: 1

    I think you may be mis-interpreting what I am saying. I am merely stating the obvious that only machine code can ultimately run on a processor.

  63. Re:Java is not slow . Does use memory by stelmach · · Score: 1
    In Computer Science compilation produces machine code. javac does not.

    Please refer to the following paragraph taken from wikipedia:
    "Most compilers translate source code written in a high level language to object code or machine language that may be directly executed by a computer or a virtual machine."
    Additionally, please refer to the description of javac taken from the javac man page:
    javac - Java compiler
    I am not stating that the JVM builds an executable and then runs it. That is surely untrue. I was just trying to explain the difference between the inner workings of a compiler verses an interpreter. The main point I was trying to make was that a compiler will hold on to the results of parsing, type checking, etc. where as an interpreter will not.
  64. Re:Great timing... by rbarreira · · Score: 1

    Maybe it's time for Id Software to start making their games with Java then. I think you know what I mean :)

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  65. Java according to Sun by owlstead · · Score: 1

    Java will never be open source.

  66. Re:Great timing... by Decaff · · Score: 1

    Maybe it's time for Id Software to start making their games with Java then. I think you know what I mean :)

    The games industry has always been rather conservative about development languages. Assembler is still much used, even those C and C++ offer high speed.

    Java should be fine for games, as there are options to use DirectX and OpenGL graphics acceleration.

  67. Java according to Sun by owlstead · · Score: 1

    "Rags" presentation had the following details. Java will never be open source. It will continue the Java community process, but it will not become open source like apache etc.

    This according to Raghavan 'rags' Srinivas at JSpring 2005 in the Netherlands where he held a nice demonstration on Java. Rags is one of the Java evangelists of Sun.

    My appologies about the wrong post before this one, that's my Dell laptop playing up (stupid touchpad gets activated by the keyboard sometimes).

  68. Re:Java is not slow . Does use memory by Anonymous Coward · · Score: 0

    Regarding VB, it supported generating native EXEs since at least 5.0. But the EXEs still need the run-time DLL.

  69. Re:Great timing... by rbarreira · · Score: 1

    Would you want to be interrupted in the middle of your game by the garbage collector? If you have used java programs you know what I mean...

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  70. Re:Java is not slow . Does use memory by Decaff · · Score: 1

    First of all, you don't compile your java code into a class file, you "compile" it. In Computer Science compilation produces machine code. javac does not.

    Yes it does. It produces machine code for the Java Virtual Machine. There are some processors that can run this code directly - it is their machine code.

    Which brings me to what I'm wondering about: You say the JVM compiles the byte code into machine code. I seriously doubt that that's true.


    It is true.

    Does the JVM really take your byte code and build an executable and spawn a process for it? Until I hear otherwise, I'm under the assumption that it does not, that rather the JVM is compiled, and that your byte code never is, but is interpreted (and cached) by the JVM.

    Just because an executable is not built an run as a separate process does not mean that byte code is not compiled. The byte code is translated into sections of machine code which are then jumped into by the interpreter (during which time it is not interpreting).

  71. Re:Great timing... by Anonymous Coward · · Score: 0

    no troll, just plain truth. go ahead troll me too it doesnt make java any faster!

  72. Re:Won't Stop Java's Slide by psykocrime · · Score: 1

    This of course, meant that Java got used for everything -- including the presentation layer of web applications where it is ridiculous. It took at over 5 years and Google's "revolutionary AJAX" to get people to start paying attention to Javascript/DHTML again.


    And all of this Javascript / DHTML is going to be generated and served how? Sure, it can be done by any platform, but Java has great support (via servlets and JSPs) for HTTP interation of this nature, so don't expect Java to disappear for that use.

    And the Web Services that the AJAX Javascript will be invoking? Where will those come from? Sure, it can be done by any platform, but Java has great support (via Servlets + WebService Endpoints, and/or Axis ) for SOAP interation of this nature, so don't expect Java to disappear for that use.

    The increase in popularity of AJAX has almost nil to do with whether or not Java remains popular. If anything, AJAX may promote Java.

    --
    // TODO: Insert Cool Sig
  73. Re:Great timing... by Anonymous Coward · · Score: 0

    We just finished major rewrites on on Java Backend replacing it all with .NET c# code, We ended up with less code and a good 10% speed increase. If anything everything I have seen says .NET is already faster and I can only see that getting better with the 2.0 release coming in a few months.

  74. Re:Won't Stop Java's Slide by NeoBeans · · Score: 1
    The only reason Java ended up dominant in enterprise web applications is that Sun pushed it in the Indian diploma mills at a time when it was fashionable among American corporate executives to stick it to American programmers who were getting close to being paid enough money to raise families in the ridiculous cost-of-living male-ghettos like Silicon Valley.

    Wow, that's a revisionist history if I ever heard one.

    Java was already popular by the time it began getting used for enterprise web applications. There was a big push to leverage Java on the server side circa 1998, and Java Servlets got a lot of positive attention because, when compared to the CGI model of forking a new process for each request, servlets were very efficient and outperformed CGI under load.

    That is why Java took off on the web tier. It offered an alternative to CGI for those who were on non-Microsoft platforms (who couldn't use ASP).

    Of course, if you just want to rant about outsourcing, you can just continue changing the story...

  75. Re:Great timing... by Anonymous Coward · · Score: 0

    Honestly, if you've completely *re-written* your product in c#, you are comparing apples to oranges. I'd also bet if you *re-wrote* your product in java, you'd see similar speed increases.

  76. Re:Great timing... by Decaff · · Score: 1

    Would you want to be interrupted in the middle of your game by the garbage collector? If you have used java programs you know what I mean...

    The garbage collection in Java can be set not to interrupt. This is why Java is now being used in real time systems.

  77. Re:Great timing... by rbarreira · · Score: 1

    Well, I still haven't understood why this game is so slow on old machines, just to give an example. Maybe it's very badly programmed, I don't know. It's great btw :)

    --

    The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
  78. Re:Great timing... by Decaff · · Score: 1

    Well, I still haven't understood why this game is so slow on old machines, just to give an example. Maybe it's very badly programmed, I don't know. It's great btw :)

    On older machines it may be using an older JVM - maybe Microsoft's one that shipped with Windows.

  79. Numbered days by pease1 · · Score: 1

    A large public website I work with is likely going to drop using java applets in the future now that the new versions of the plugin display a very large ad for Sun - and even seem to delay the running of the applet to ensure you get a good 10 or 15 second stare at the ad.

  80. Who downloands just a .class file? by autopr0n · · Score: 1

    I havn't written a java application that came as one .class, um, ever. And I'e also never written one that had *any* trouble on other platforms.

    Of course in the "real world" you're going to need to do some native code, maybe some database stuff, and those arn't protable all the time. But you can't blame java for that.

    --
    autopr0n is like, down and stuff.
  81. Libraries by Mark_MF-WN · · Score: 1
    Libraries are totally fair game. Otherwise we'd have to say that C is the worst language ever developed -- it has no gui or networking components whatsoever! The fact that Java comes with a robust, full API shouldn't make its support for potentially superior 3rd party libraries any less relevant.


    So, in the vein of the original poster, I'm going to claim that Java is the best 3G application-development language going: it's the only one that includes GUI components of any kind in its API (except maybe Microsoft's C# API, which is debatable). Sounds pretty silly huh?