◆ C: C helps us learn how to consider problems at the hardware system level. His best practice is resource efficiency and proximity to machine language. The worst thing is that its programming is actually the purgatory of resource management.
◆ C: C helps us learn how to consider problems at the hardware system level. His best practice is resource efficiency and proximity to machine language. The worst thing is that its programming is actually the purgatory of resource management.
Instance: fetchmail
◆ C ++: The best practice is the compilation efficiency and the combination of object-oriented and generic programming. The worst thing is that it is very weird and complicated, and often encourages overly complicated design.
Example: Qt toolkit
◆ Shell: the best thing is that it is very natural and fast to write small scripts. The worst thing is that large shell scripts must rely on a large number of auxiliary commands, which do not necessarily have the same or even different performance on all target machines.
Instance: xmlto
Sorcery Linux
◆ Perl: the enhanced shell. The best practice is to use it as a powerful tool for a large number of small glue scripts involving regular expression matching. The worst thing is that when the program is large, Perl will become very ugly, rigid, and almost impossible to maintain.
Instance: blq (small), keeper (large)
◆ Tcl (Tool Command Language): a small language interpreter that is designed to be connected to C compiling, and provides Script Control (extended script) for C code ). Its best practice is its frugal, compact design, and the scalability of the Tcl interpreter. The worst part is its odd location analyzer and weak data structure and namespace control.
Instance: TkMan
Moodss
◆ Python: The best practice is to encourage clear and easy-to-read code. it is easy to learn and use, and can be expanded to large projects. The worst thing is that it is not only less efficient than the compiling language, but also slower than other scripting languages.
Instance: imgsizer
Fetchmailconf
PIL
◆ Java: The best thing is that it is very close to the goal of "writing once and running everywhere" and is very useful as an environment independent of the operating system. The worst thing is that the split of Java1/Java2 impairs the implementation of this goal.
Instance: FreeNet
◆ Emacs Lisp: The best practice is to combine the basic language Lisp, which is very effective for text operations. The worst is poor performance, making it difficult to communicate with other programs.