It's written in front of you.

My brother Todd is currently working on a shift from hardware to programming. I have reminded him that the next big revolution will focus on genetic engineering.
Our microbial technology will be able to make food, fuel and plastic, they are clean, do not pollute, and can further human insight into the mysteries of the physical world. I think the progress of the computer will be insignificant in comparison.

But then I realized that I was committing some of the mistakes that science fiction writers often make: Lost in technology (something that happens in science fiction)! If you are an experienced writer, you will know that you must not be a person. Heredity has a great influence on our lives, but it is not quite certain that it can erase the effects of the computer revolution-or at least the information revolution. Information involves communication between people: indeed, the inventions of automobiles and wheels are very important, but they are the end of all. What is really important is our relationship with the world, and the key is communication.

The book may be able to explain some of the problems. A lot of people think I'm a little bold or a little arrogant, and I put all my possessions on the web. "Who else is going to buy it?" he said. "They asked. If I were a very old-fashioned person, I would never do so. But I really don't want to write a computer reference book again along the old road. I don't know what will happen in the end, but I do think it's the smartest decision I've made on a book.

At least one thing is for sure, people are starting to send me corrective feedback. This is a shocking experience, because readers will see every corner of the book and find out the techniques and grammatical errors that are deep in their hiding place. Thus, unlike other books published in the traditional way, I will be able to correct all known categories of errors in a timely manner, instead of having them eventually printed as type and appearing in front of you. As the saying goes, "lookers-on, the spectators." People are very sensitive to the mistakes in the book, and are often very polite to point out: "I want to say this is wrong, my view is ...". After careful study, I often find that I do have something wrong, which I did not realize at the time of writing (how many times I can't check it). I realize that this is a welcome reflection of the strength of the group, and it makes the book seem really different.

But then I heard another voice: "Well, the electronic version you put there is really creative, but what I want is a version of the print from the real publisher!" "In fact, I've made a lot of effort to get a good reading from a regular printer, but it's still not as formal as a really printed book," he said. Many people do not want to see the whole book on the screen, nor do they like to read with a pile of paper. No matter how good the print format is, these people like to be still the real "book" (The laser printer's cartridge is also too expensive a bit). It now seems that the computer revolution has not yet made the publishing press completely out of the traditional model. However, one student recommended a model for future publishing: Books will be published on the internet first, and then printed on paper only if absolutely necessary. At present, a large number of book sales are not very ideal, many publishers are at a loss. But if published in this way, it becomes much more flexible and easier to ensure profitability.

This book also gives me profound enlightenment from another angle. I started off thinking that Java was "just another programming language." The idea is set up in many cases. But as time went on, I learned more about it and began to realize that its basic purpose was different from all the other languages I'd seen.

Programming has a lot to do with the manipulation of complexity: the complexity of a problem that is ready to be solved depends on how complex the machine is. It is because of this complexity that our program design projects fail frequently. For all the programming languages I've been exposed to before, they haven't skipped the box, and it's decided that their main design goal is to overcome the complexity of program development and maintenance. Of course, many languages have been designed to take into account the complexity of the problem. But from another point of view, there must be some other problems in the actual design that need to be taken into account in this complex issue. Inevitably, the rest of those problems will eventually become the most annoying programmers. For example, C + + must be backward compatible with C (so that C programmers can adapt to the new environment as quickly as possible), while also ensuring the efficiency of programming. C + + in both aspects of the design is very good, for it won a lot of reputation. But they also expose additional complexity that hinders the success of some projects (of course, you can blame programmers and management, but if a language can help by capturing your errors, why not do it?) ）。 As another example, Visual Basic (VB) has a close connection with the original basic. And basic does not intend to design a comprehensive solution to the problem of the language, so the heap added to VB all the extensions have caused a headache and difficult to manage and maintain the syntax. On the other hand, C + +, VB and other languages, such as Smalltalk, have a hard time with complexity. As a result, they are very successful at solving specific types of problems.
I really feel shocked when I understand that Java's ultimate goal is to ease the burden on programmers, although its subtext seems to be that "we don't care about anything other than shortening the time and making it harder to produce robust code." "At this early stage of the present, the consequence of achieving that goal is that the code does not run very fast (although there are many assurances that Java will eventually run so fast), it does shorten the development time to a surprising level--almost only half or even shorter time to create an equivalent C + + program. This saving time can produce even greater benefits, but Java is not the only part of it. It is even higher and encapsulates all the complex tasks that are increasingly important, such as web programs and multithreading. The various language features and libraries of Java can make those tasks easy to accomplish at any time. And finally, it solves some of the more complex problems that are really difficult: cross-platform programs, dynamic code changes, and security, among other things. In the past, any one of them can make your head as big as a bucket. So no matter what performance problems we see, the Java warranty is still very effective: it makes programmers significantly more efficient at programming!

In my opinion, the most important effect of programming efficiency is the web. The web design was very difficult before, and Java made the problem easy (and Java is constantly progressing, making it easier to solve such problems). The design of Web programs requires us to communicate more efficiently with each other, and at least cheaper than telephone communications (only e-mail offers benefits for many companies). As we communicate more and more on the internet, shocking things can take place, and they are surprisingly no less than the shock of the Industrial revolution.

In all aspects: creating programs, scheduling programs, constructing user interfaces, enabling programs to communicate with users, running programs on different types of machines, and conveniently writing programs that enable them to communicate--java through the Internet to improve the "communication bandwidth" between people. And I think the result of the communications revolution may not be simply the sheer number of bits that are going around. We think recognizing where the true revolution takes place, because communication between people becomes more convenient-between individuals and individuals, between individuals and groups, between groups, and even between planets. It is predicted that the next great revolution will occur because enough people and enough connections are made, and this revolution is based on the whole world. Java may or may not be a direct factor in the revolution, but I feel at least doing some meaningful work here-trying to teach you an important language!