A Quote by Miguel de Icaza

I was interested in Java the beginning, but the problem with Java is you do have to switch your platform. — © Miguel de Icaza
I was interested in Java the beginning, but the problem with Java is you do have to switch your platform.
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.
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.
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.
Java isn't platform independent; it is a platform
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.
From the point of view of the people who are using the platform, one of the most valuable things about Java is the consistency, the interoperability.
I fear - as far as I can tell - that most undergraduate degrees in computer science these days are basically Java vocational training. I've heard complaints from even mighty Stanford University with its illustrious faculty that basically the undergraduate computer science program is little more than Java certification.
I believe strongly that a group's potential is eventually limited by the strength of its leadership. I'm an outsider, but it still looks to me like the leadership in the Java w orld is Fouled Up Beyond ALL Recognition. Java ISVs don't know whether to listen to Mom or Dad. Everybody knows IBM should just buy Sun and clean up the mess. When are they going to do it?
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.
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.
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.
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.
High-end BREW phones aren't nearly as limited a gaming platform as you might think - they are a lot more powerful than an original Play Station, for example. Java phones, however, are saddled with a huge disadvantage for gaming.
I've never worked with the Java community.
Java is C++ without the guns, clubs and knives.
A class, in Java, is where we teach objects how to behave.
This site uses cookies to ensure you get the best experience. More info...
Got it!