James Gosling was born in Canada and is a computer programming genius. When he was 12 years old, he was able to design his own video game console or help neighbors repair harvesters.
At University, Gosling worked as a project development student in the Department of Astronomy, University of Calgary, Canada. He received a bachelor's degree in computer science in 1977 and a doctorate in computer science from Carnegie Mellon University in 1983. During his PhD in computer science at Carnegie Mellon University, he wrote Gosling Emacs, an Emacs-like editor that runs on multiple computers. -The processor version of the Unix operating system (written in C, using Mocklisp as an extension language).
After graduation, Gosling went to work for IBM and designed the first-generation IBM workstation NeWS system, but it did not get the attention of the company's leaders, which also led him to later switch to Sun.
In 1991, while working at Sun, James and a group of technicians created a project called Oak, aiming to develop a programming language that runs on a virtual machine while allowing programs to run on multiple platforms, such as TV set-top boxes. Later, this work evolved into Java. With the popularity of the Internet, especially the emergence of Web browsers developed by Netscape, Java has become the most popular development language in the world. So James Gosling is called the father of Java. At the end of 1994, James Gosling demonstrated the Java program at the "Technology, Education, and Design Conference" held in Silicon Valley. In 2000, Java became one of the most popular computer language in the world.
Gosling, the father of Java, created a great programming language-Java, which ranks first in the TIOBE rankings all year round. In addition to Java, he also developed a satellite data acquisition system, a multi-processor version of Unix, several compilers, a mail system, and a window manager. He also implemented Gosling Emacs in C, which was the first editor similar to Emacs on Unix. Gosling once talked about the art of computer programming. He believes that this is the same as the principle of energy conservation: the more energy you put into the program, the less trouble and tossing energy users will encounter when using it. It is to balance the complexity of development and users as much as possible between the development side and the user side.