Modular programing and GUIs

That makes no sense...

Yes, absolutely

No, It will crash!

In specific conditions.

Procedures are sets of instructions that can be re-used. Both procedures and functions can be passed parameters, and both can return values.

In computer programming, a procedure is a set of coded instructions that tell a computer how to run a program or calculation. Both procedures and functions can be passed parameters. However, a function only is a procedure that returns values.

Procedures may use functions and other computer programming constructs to achieve a goal. Like functions, parameters can be passed to procedures.

Computer procedures different from functions, as procedures can only be run once. However, procedures may or may not return values, depending on its use in a program.

It requires to think harder about how to solve a complex at first. Planning is essential as the programmer needs to figure out how to solve the problem. Then it becomes much easier to write the code.

Procedural programming is more efficient for event-driven programs, where user input is necessary for the program to run. But overall the program is much longer to write as a team work will need more of code writing.

This type of programming technique is preferred by professional computer programmers because it has less bug at the end, even though it requires more code to write.

Splits complex problems into several smaller problems. It allows for team work. It is much more maintainable, expandable, and easier to debug. However it requires extensive testing to ensure fail-proof.

It takes advantage of all the digital input devices available (mouse, turnball, touchscreen, joystick, etc.) to control visually whatever icon or other object needs to. However, it requires much more processing and memory resources to achieve its objectives.

All modern computer devices do require a GUIs which make life easier for the users. However it is of no use for disabled users, especially the physically or visually impaired users. Whereas, a voice-controlled interface needs no GUI and a command line interface would be most useful in that case.

Actually a command line interface is much more appealing to professionals who like working at the machine level for its faster response time. Besides, there is less risk of bugs and malware infections.

Command line interfaces are less prone to runtime errors and malware infections because they are basic structure compares to a GUI. But GUIs are more efficient because they offer more options to user to choose from.

A command line interface is more prone to runtime error, due to the fact that the code is less robust than the code processing a GUI.

In a GUI, the code is more prone to runtime errors because of the extra code required to manage the interaction with the user.

The command code remains strictly the same, except that a GUI requires extra code to handle events such as buttonClicked, or mouseMoved, or screenTouched. For a GUI, the code must interact with the relevant driver(s).

The size of the command code increases dramatically because of the overhead code to work out what to do with the relevant icons affected.

GUIs are used in many applications, but they are require extra hardware to run properly. Whereas command line interfaces cannot run on modern computer devices.

People have habits and prefer known routines that they liked. So many professional programmers would prefer one type of interface over the over as a result. Command line interfaces can run on any computer device.

Command line interfaces are used only in under-developed societies because computers are old and Operating Systems are not capable of handling GUIs.

The majority of people prefer a GUI to a command line interface. Only old people still use command line out of ignorance.