(ThinkInJava, an introductory tutorial for java! I hope it helps us! This book also gave me in-depth inspiration from another point of view. When I first started I thought Java was "just another programming language". This idea is built in many situations. But as time went on, I learned more about it and came to realize that its basic purpose is different from any other comprehensive language I've seen. Programming has a lot to do with controlling complexity: for a problem to be managed, its complexity depends on the complexity of the machine used to manage it. It is because of this clutter that our programming projects fail repeatedly. Regarding the comprehensive programming languages ??I have ever touched, none of them can skip this box, which determines that their primary design solution is to overcome the complexity of program development and maintenance. Of course, many languages ??are designed with complexity in mind. But from another point of view, there are bound to be other problems that manifest in practical design, and they need to be considered in this messy problem. Inevitably, those other problems end up being the most frustrating for programmers. For example, C must maintain backward compatibility with C (so that C programmers can get used to the new environment as quickly as possible), while ensuring the efficiency of programming. C is well designed in both of these respects, earning a lot of reputation for it. But together they also expose an extra level of clutter that prevents some projects from being successful (of course, you can blame the programmers and management, but assuming a language helps by catching your mistakes, why does it Why not do that?). As another example, VisualBasic (VB) is closely related to the original BASIC. However, BASIC has no program designed to be a language that can comprehensively manage the problem, so the comprehensive extension added to VB has formed a syntax that is troublesome and difficult to manage and maintain. On the other hand, C , VB, and other languages ??such as Smalltalk all work on the problem of complexity. The result is that they are very successful in managing certain types of problems. I was truly shocked when I realized that Java's ultimate solution was to lighten the programmer's burden, although its subtext seemed to say: "We don't care about other things other than shortening the time and making it easier to generate robust code. Any work that doesn't work." At this rudimentary stage now, the result of getting to that scheme is that the code doesn't run exceptionally fast (although there's a lot of assurance about how fast Java will run one day after all), but it does reduce the development time to Amazing situation - it takes almost half or less time to create an equivalent C program. This time saved can yield greater benefits, but Java doesn't stop there. It even goes a step further, encapsulating comprehensive complex commands that are increasingly important, such as network programs and multi-threaded management. Java's various language features and libraries make those commands readily available at all times. And finally, it manages some of the clutter of real parts of the difficulty: cross-modal programming, dynamic code conversion, and security maintenance, to name a few. In the early years, any and every one of them can make your head as big as a bucket. So no matter what functional problems we see, Java's guarantee is still very effective: it enables programmers to significantly improve the efficiency of programming! In my opinion, the Web is the most affected by the improvement of programming efficiency. Network programming used to be difficult, and Java has made this problem easy to manage (and Java is making progress to make managing such problems easier). The design of web programs requires us to communicate with each other more efficiently, and at least less expensive than telephone communication (e-mail alone has brought benefits to many businesses). As we communicate more and more online, startling jobs will happen, and they will be as surprising as the original industrial revolution. In all aspects: creating programs; programming programs; structuring user interfaces so that programs can be exchanged with users; running programs on different types of machines; and easily writing programs to communicate over the Internet—Java improves The "communication bandwidth" between people. And I thought that the results of the communications revolution might not be simply a huge number of bits being passed around. We think we can see where the real innovation takes place, because the exchanges between people become more convenient - between individual and individual, between individual and group, between group and group, and even between planets. Some people predict that the next big revolution will happen because enough people and enough interconnections are formed, and this innovation will happen on the basis of the whole world. Java may or may not be a direct factor in facilitating that innovation, but I at least feel like I'm doing some meaningful work here - testing teaches us an important language!
ThinkInJava.chm)
收藏
