James Gosling
Canadian computer scientist who created the Java programming language at Sun Microsystems; later at Google, Liquid Robotics and Amazon Web Services, from which he retired in 2024.
James Gosling did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
-
Their wordsI certainly think that the patent system is broken, but the system is what it is. The original basic theory makes sense to me, but what it's evolved into doesn't. At Sun we had a near death experience after losing a case with IBM, after that we realized we had to play the game, no matter how bogus.
↗Comments around Oracle v Googlenighthacks.com 1st of 4 in this piece
-
Their wordsThe wide implications of Oracle winning the copyright case are pretty disturbing. But that's a practical opinion. How it will go in the legal system is anyone's guess. It extends far beyond Oracle: developers everywhere use APIs defined by many other entities. I hate to think of what an emerging "copyright troll" industry might be.
↗Comments around Oracle v Googlenighthacks.com 2nd of 4 in this piece
-
Their wordsDespite my well-known opinions on Oracle, they wouldn't do any of the nightmare scenarios that some have imagined: such a meltdown would not be in their own self interest. They have actually been unexpectedly good stewards of Java (although less so of Solaris).
↗Comments around Oracle v Googlenighthacks.com 3rd of 4 in this piece
-
Their wordsThe issue has always been interoperability. It's one of the major aspects that has made the Java community thrive. The freedom of developers to expect their programs to work has always been at tension with the freedom of platform providers to do whatever they please. At Sun, we always sided with developers.
↗Comments around Oracle v Googlenighthacks.com 4th of 4 in this piece
- 3 days earlier
-
Their wordsJust because Sun didn't have patent suits in our genetic code doesn't mean we didn't feel wronged. While I have differences with Oracle, in this case they are in the right. Google totally slimed Sun. We were all really disturbed, even Jonathan: he just decided to put on a happy face and tried to turn lemons into lemonade, which annoyed a lot of folks at Sun.
- 14 months earlier
-
Their wordsFor most people, this class of transformations should be avoided like the plague they are. But for folks like me who all too often need to do intense tuning, they are necessary. Can they be made cleaner? It's a pity that refactoring is viewed purely as something done in an IDE.