Why would you implement Visual Basic? What is its history? Does it serve a greater purpose?
A programming language and environment developed by Microsoft. Based on the BASIC language, Visual Basic was one of the first products to provide a graphical programming environment and a paint metaphor for developing user interfaces. Instead of worrying about syntax details, the Visual Basic programmer can add a substantial amount of code simply by dragging and dropping controls, such as buttons and dialog boxes, and then defining their appearance and behavior. Although not a true object-oriented programming language in the strictest sense, Visual Basic nevertheless has an object-oriented philosophy. It is sometimes called an event-driven language because each object can react to different events such as a mouse click. Since its launch in 1990, the Visual Basic approach has become the norm for individuals interested in learning how to start developing software. Visual Basic sometimes called a Rapid Application Development (RAD) system because of its ability to enable programmers to quickly build prototype applications. Visual Basic demonstrates learning software development is not difficult. Once mastered, progressing to another programming language is painless, straightforward, and effortless.
What is SQL? What is its purpose?
SQL (pronounced "ess-que-el" or "see-kwell") stands for Structured Query Language. SQL is used to communicate with a database. It is the standard language for relational database management systems. SQL statements are used to perform tasks on a database like: retrieving, updating, moving, modifying, or even controlling data within the database. Some common relational database management systems (DBMS) that use SQL are: Oracle, MySQL (#1 for websites), Microsoft SQL Server, PostgreSQL, Microsoft Access, SQLite, etc. Although most database systems use SQL, most of them add additional proprietary extension statements that are usually only used on their system.
Why should you chose to design software with C# instead of Java?
Determining which language you wish to embrace requires knowledge of the environment in which C# and Java operate. Let's take a look at the major difference between C# and Java. While open-source implementations exist, C# uses the .NET framework which requires external (not from Microsoft) tools to access. Java's source code became widely available thanks to Google's importation of it to Android (an operating system for phones). C#'s support and implementation of delegates, also known as pointers, is effortless. To achieve the same operation in Java, you must create an interface with a single method or devise another workaround which could require a nontrivial but tedious amount of additional code. If you take a look at the exact methods of operation and functionality of C# compared to Java, you will notice C#'s syntax elegantly presents itself in an easy to read manner, while Java declarations are cluttered and filled with what is called 'noise' . C#'s friendly native constructs such as Types, Properties and Events which make reading a document efficient, effortless, and easy. Opening a Java project for the first time can be painful on the eyes and the brain because of the queer learning curve (and that is just one project). The exceptions thrown through C# are not checked, meaning it is up to the developer to "catch" the thrown errors—this leads to more flexibility for the developer. Does he want to close the application? Notify the user? Fix the error himself? C#, using the .NET Framework, implements garbage collection which operates as the name suggestions—it allows the developer to not worry about having to free memory, allocates objected on the heap efficiently, reclaims objects and replaces with empty space (ready to use), and provides memory safety by ensuring an object cannot use the content of another object. While Java by default is cross-platform and C# (without any external help) is heavily integrated into Windows, Java's cross-platform implementation has been regarded as troublesome and complex depending on which operating system you're trying to develop on. Another few reasons C# should be preferred over Java are: the support of native resource-management idiots (also known as the 'using' statement), syntax allows for Lambda and LINQ expressions which allow for much shorter and easier to read code, explicit generic covariance and contravariance, dynamic variables, and much better enumeration support with the 'yield' statement.