Slashdot Mirror

← Back to Stories (view on slashdot.org)

"MS Killed Java" (on the Client) JL Founder

Posted by Hemos on from the killing-the-pool dept.

jgeelan writes "In a commentary titled "Microsoft Killed Java" the founder of JavaLobby, Rick Ross, revisits the 'death' of Java on the client. "Five years ago, almost to the day," Ross declares, "Microsoft shipped IE4 with a JVM that was intentionally engineered to provide leverage to corrupt and pollute Java compatibility standards." According to an Associated Press report, Microsoft Corp has until only October 4 to respond to Sun Microsystems' request for a federal court injunction requiring Microsoft to integrate Java into Windows."

3 of 641 comments (clear)

  1. Okay... and...? by ObviousGuy · · Score: 1, Flamebait

    Yes, Java is dead on the client.

    Sorry about that.

    I'm sure everyone and their brother putting stupid Java animations on their website and generally bringing poor 28.8 modems to a grinding halt had nothing to do with its poor reception.

    --
    I have been pwned because my /. password was too easy to guess.
  2. MS didn't kill Java by Anonymous Coward · · Score: 1, Flamebait

    Come on, now. Microsoft didn't kill Java on the client. Java killed itself through confusing procedures, poor performance, repeated incompatible upgrades, costly support requirements, and expensive development tools. Java was sitting on the edge of its coffin. All Microsoft did was use its toe to push it in.

  3. Oh bullshit by joss · · Score: 1, Flamebait

    What killed Java on the client was the fact that it was shit.

    First there was AWT - ugly damn toolkit. Then after people had moved heaven and earth trying to produce vaguely useable applications with AWT, they came out with SWING. This had a huge learning curve, it produced extremely verbose code, it was painfully slow, and in it's earlier versions it was infested with bugs.

    Thousands of developer years went into producing java applications. These applications were, almost without exception, shit. The few that actually made it out to the public "felt" like java applications. With a ten fold increase in RAM and processor speed, these java applications were almost useable, but still felt slower than equivalent C programs on one's old box.

    If anything, MS encouraged java by coming out with libraries[MFC] and languages[VB] that were so bad they made java look worthwhile. Their malevolent business practices were amply compensated for by their technical incompetence.

    A plague on both your houses...

    --
    http://rareformnewmedia.com/