Slashdot Mirror

← Back to Stories (view on slashdot.org)

Interview With James Gosling

Posted by Hemos on from the learning-more-about-hjava dept.

Def Mango Raygun writes "There is an interview with James Gosling of Sun. He talks about some language features and why they happened. It's short, but informative"

11 of 216 comments (clear)

  1. length by billnapier · · Score: 5, Funny
    It's short, but informative.
    Unlike the text of this submission, which is only one of those.
  2. Huh? by swagr · · Score: 5, Funny

    So the JDC interviewed James Gosling. Surely he [has] contributed to the JDC and has a log in, thus making him a part of the JDC collective...

    Next week on Slashdot: Taco interviews himself.

    --

    -... --- .-. . -.. ..--..
    1. Re:Huh? by tswinzig · · Score: 5, Funny

      So the JDC interviewed James Gosling. Surely he [has] contributed to the JDC and has a log in, thus making him a part of the JDC collective...

      Next week on Slashdot: Taco interviews himself.

      The difference is this interview is interesting, and James Gosling knows how to spell.

      --

      "And like that ... he's gone."
  3. Short, informative, and funny! by foobar104 · · Score: 5, Funny

    This interview is worth reading if only to get a laugh out of the way Sun's marketroids obviously sanitized it. In at attempt to make the text of the interview (which is just a transcript of a spoken exchange, after all) comply with Sun's trademark guidelines, they ended up with sentences like this:

    So, personally, you could delete [the] JDBC [API] from [the] J2SE [platform] and it would not affect any code that I've ever written.

    And this:

    That would make [the] Java [programming language] much more flexible.

    And this:

    Is it possible to submit the Java [technology] bytecode specification to a standards body like ECMA [and the like]?

    Sheesh. This interview was brought to you by the letters "[" and "]".

    1. Re:Short, informative, and funny! by pnatural · · Score: 3, Funny

      there are important technical differences between Java the language and Java the set of frameworks

      which is why they're all called Java (TM).

    2. Re:Short, informative, and funny! by Anonymous Coward · · Score: 1, Funny

      I was working at JavaSoft shortly after 1.0 came out. The trademark police had just sent a long message around about how to properly use the Java trademarks, including adding [TM] in the right places and refering to everything as "Java Technology".

      In response one of the developers sent out a spoofed message about name changes to popular parts of the platform:

      java -> java[tm]technologybytecodeinterpreter
      javacc -> java[tm]programminglanguagecompiler

      and so on.

      The powers in change where not amused.

  4. [The] editing [job] by Anonymous Coward · · Score: 5, Funny

    I think [that] the [person who acted in the capacity of the] editor [of this article] who keeps [repeatedly] butting in [to the questions and answers] for no [descernable] reason [or benefit] should just shut [the f*ck] up.

  5. hjava? by sarcast · · Score: 1, Funny

    I looked at the topic of this article and saw the usually witty one liner below that says:

    from the learning-more-about-hjava dept.

    And I thought to myself, what is this new fangled hjava that I have heard nothing about and what is there to learn?

    Then in my excitement, I realized it was just a typo...

  6. Does Java use Pointers? by Anonymous Coward · · Score: 0, Funny



    I have read that one good thing about Java is that it does not rely on pointers for memory management. Is that true?

    Also, I recently have begun a C++ class and on the subject of pointers, the textbook says this:

    Never dereference the "NULL" pointer.

    Well, after reading that, I decided that -- being a total programming geek after all :) -- the VERY FIRST THING I wanted to try to do was to "dereference" this NULL pointer.

    Unfortunately, the textbook did not go into detail about how this could be accomplished -- no surprise there.

    So can someone tell me what the probably outcomes of dereferncing &NULL would be? Is it really as dangerous as the book's author suggests?

    (It occurred to me that it might have a similar effect to something that I read about a while, back -- "Tao of Windows Buffer Overflow" -- this article. )

    So does anyone here know how to "dereference the NULL pointer"?

    I would appreciate some detailed sample code.

    If I am going to dereference *NULL, I want to make sure that I am doing it the correct way.

  7. Questions left unanswered... by Bonker · · Score: 5, Funny

    1. Why is Java so damn slow?

    2. Why do so many Java developers get so upset when you point out how damn slow Java really is?

    3. Why is it so much fun to pick on Java developers when there really are slower languages out there?

    4. If you could make Java fast, would you voluntarily leave it slow just so we could give Java developers apoplexy by mentioning how fast even PHP is for certain tasks?

    --
    The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
  8. My Favorite Java Quote... by pnatural · · Score: 3, Funny
    I should post this anon because I'm sure I'll be marked down by the moderators/java coders with no sense of humor, but it's only karma. Here goes:
    If code were music, Java would be country.
    Anyone know where I could get that on a teeshirt?