JAMES GOSLING

Simply put, when you have very large pieces of software, most of the tools look at the individual lines of code as text. It is often extremely powerful to look not at individual pieces of code but at a system as a whole.

The data center side of the world is kind of like a solved problem, but you see interesting things happening on the edge with things like cell phones and embedded systems that are becoming really fascinating.

I enjoy evangelizing Java. In my heart of hearts, I'm an engineer, and what makes me happy is building something that works and having someone use it. That's cool.

The whole thought of a career with computers - given that hardly anybody even knew what they were - it wasn't even a concept.

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.

One of the things that Java is good at is giving you this homogeneous view of a reality that's usually very heterogeneous.

The notion of having a fleet of autonomous ocean-going vehicles wandering the world collecting data is something out of fiction.

I've made the comment that democracies work slower than dictatorships. That's a true thing.

I like to bitch and moan about lawyers, but they often have actually good points.

My impression is that a really, really high-order concern for the whole development community is interoperability and consistency.

I didn't do programming language stuff in college at all.

Some of these isolated applications that sit on one machine are a million lines of code. How do you deal with that? Most people have no way to wrap their head around it.

If you look at our customers, our customers tend to be really high-end people who make big, sophisticated systems.

I had half my family that were farmers, and I was really pretty good at repairing farm equipment. There was certainly a period of time where I would have been happy to do that, just to be a farm equipment repairman in Dalemead, Alberta.

The nerves were so badly compressed that I had no feeling on the palm of my hand. I mean, you could have pounded a nail through my hand and I wouldn't have been able to feel it.

If you want to write the software to control the national medical system of a large country, Java is perfect.

You see people doing Java-based internal applications all over the place, regular desktop applications that are sort of front-ends to the things in the back, or standalone things.

The way that NetBeans is architected, it's not so much a tool as a tool environment.

In C there are no data structures: there are pointers and pointer arithmetic. So you have a pointer into a data structure.

I've always felt that sort of in the abstract, open-source is the right thing to do for a lot of the kinds of things that we do. There are a variety of issues that make it a very complex discussion as to whether it actually works as a business.

Anytime someone builds a little application that runs on a cell phone, there's something that goes on the server.

When you interview at Google, they don't tell you what the job is. You get hired for a pool and the reason they do it that way is they don't want outsiders learning their secrets in the interview process.

The thing that the Microsoft folks did a really good job of is the easy-to-use tools for making application-building simple.

Most developer tools try to shield you from actually writing code in constructing the GUI bits or the database bits. Yet when you do write code you usually get glass teletypes where high tech is keyword coloring.

The asparagus effect is what happens sometimes when you render 2D images into 3D.