56 Quotes by James Gosling

  • Author James Gosling
  • Quote

    One of the Microsoft representatives in attendance admitted that unilateral language extensions would be detrimental and said that Microsoft 'wouldn't be cowboys' by unilaterally introducing such extensions in their implementation of Java.

  • Tags
  • Share

  • Author James Gosling
  • Quote

    I am aware of no PC manufacturer that is presently shipping a second, compatible JVM on their Windows systems,

  • Tags
  • Share



  • Author James Gosling
  • Quote

    All of us who attended the meeting -- including Microsoft -- unanimously agreed that unilaterally extending the Java programming language would hurt compatibility among Java tools and programs, would injure other tools vendors, and would damage customers' ability to run a Java-based software product on whatever platform they wished,

  • Tags
  • Share

  • Author James Gosling
  • Quote

    SOAP and XML have often been characterized as HTML (Hypertext Markup Language) for silicon-based life forms. An HTML that is readable by software,

  • Share

  • Author James Gosling
  • Quote

    During the integration meetings between Sun and Oracle, where we were being grilled about the patent situation between Sun and Google, we could see the Oracle lawyer's eyes sparkle.

  • Share

  • Author James Gosling
  • Quote

    All of us who attended the meeting - including Microsoft - unanimously agreed that unilaterally extending the Java programming language would hurt compatibility among Java tools and programs, would injure other tools vendors and would damage customers' ability to run a Java-based software product on whatever platform they wished.

  • Tags
  • Share

  • Author James Gosling
  • Quote

    In the Java world, security is not viewed as an add-on a feature. It is a pervasive way of thinking. Those who forget to think in a secure mindset end up in trouble. But just because the facilities are there doesn't mean that security is assured automatically. A set of standard practices has evolved over the years. The Secure Coding Standard for Java is a compendium of these practices. These are not theoretical research papers or product marketing blurbs. This is all serious, mission-critical, battle-tested, enterprise-scale stuff.

  • Tags
  • Share