First thing first, IDE consists of a source code editor, automatic build tools, and a debugger. Most IDEs have intelligent code auto-completion. Some IDEs contain a compiler, an interpreter, or both, such as NetBeans and Eclipse, but others do not, such as SharpDevelop and Lazarus. The boundary between an IDE and other parts of the broader software development environment is not well defined. Many times, in order to simplify the construction of the graphical user interface (GUI), a version controller system and various tools are integrated.
IDEs are designed to maximize programmer productivity by providing tightly knit components with similar user interfaces. IDEs feature a single program in which all development takes place. Generally, this program tends to offer many features for the creation, modification, compilation, deployment and debugging of software, which means that one of the purposes of the IDE would be to reduce the configuration necessary to rebuild multiple development utilities.
But then, what is the IDE for and what is it when talking about visual programming?
Well, a Visual IDE allow users to create and program new applications in motion, building blocks, or code nodes to create flowcharts or structure diagrams that are then compiled or interpreted. These flowcharts are often based on the Unified Modeling Language.
The truth is that at this time, this programming method is used for almost all programmers and is being used to develop software such as video games, operating systems, apps, etc., the only difference is that each of those is programmed with a different IDE or code editor of choice, depending on tastes and convenience for each of the programmers or companies.
