A Quote by James Gosling

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.
I was interested in Java the beginning, but the problem with Java is you do have to switch your platform.
This evolution may compromise Java's claim of being simpler than C++, but my guess is that the effort will make Java a better language than it is today.
If I were to pick a language to use today other than Java, it would be Scala
Java and C++ make you think that the new ideas are like the old ones. Java is the most distressing thing to hit computing since MS-DOS.
Java the language is almost irrelevant. It's the design of the Java Virtual Machine. And I've seen compilers for ML, compilers for Scheme, compilers for Ada, and they all work. Not many people use them, but it doesn't matter: they all work.
If Java had true garbage collection, most programs would delete themselves upon execution.
While Microsoft does not share all of Oracle's ambitions for Java, we agree that it is a very valuable tool for software developers.
I think it would be a tragic statement of the universe if Java was the last language that swept through.
However, when Java is promoted as the sole programming language, its flaws and limitations become serious.
We think we're going to be especially strong in platform where we have our two platform brands: our database brand is the Oracle Database 12c, and our programming language brand is this thing called Java.
No one wants one language. There are applications when it's appropriate to write something in C rather than in Java. If you want to write something where performance is much more important than extensibility, then you might want to choose C rather than Java.
When you choose a language, youre also choosing a community. The programmers youll be able to hire to work on a Java project wont be as smart as the ones you could get to work on a project written in Python. And the quality of your hackers probably matters more than the language you choose. Though, frankly, the fact that good hackers prefer Python to Java should tell you something about the relative merits of those languages.
When you write a program for Android, you use the Oracle Java tools for everything, and at the very end, you push a button and say, Convert this to Android format.
When you write a program for Android, you use the Oracle Java tools for everything, and at the very end, you push a button and say, 'Convert this to Android format.'
Java development without a little heresy would be a dull place, and a dangerous one.
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.
This site uses cookies to ensure you get the best experience. More info...
Got it!