Armed with the knowledge gained from the examples in this book as a guide, and a copy of Nye (Xlib Programming Manual for Version 11, O’Reilly & Associates, Inc., Sebastopol, 1995), and particularly Nye (Xlib Reference Manual for Version 11, O’Reilly & Associates, Inc., Sebastopol, 1993), useful programs can be written using Xlib. The argument against doing so is the use of toolkits makes programming easier and quicker, and the result is visually appealing. Although the programming may be quicker to write using a toolkit due to the written application code being shorter in length than when using by using Xlib, its execution time generally is slower. Toolkits are the analogue of a compiler while Xlib is the analogue of an assembler, and to squeeze the most out of hardware, an assembler is the better choice but at the cost of programming effort. Xlib programs generally use fewer CPU instructions and make more efficient use of the X Protocol than toolkit programs do. So if a program is to have large usage, then the use of Xlib instead of a toolkit may be a better design decision across the lifetime of the program.