ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Now this is interesting - just the other day I came across a tutorial that insisted that API stood for Applications Programmer Interface, which is just a little different. Given the definition in the Wikipedia, it makes sense to think of it as the interface between the application and the programmer.
I wish I could find the reference (tried - came up empty).
Nah - the interface between a programmer and an application is called an IDE (in the sence of "Integrated Design Environment" rather than "Integrated Drive Electronics".) Then there's JAVA programming.
The interface between a user and the application is called a UI.
The API is well thought of as the interface between that application and the rest of the computer... but it is more complicated than just that. You get a feel for them when you use them.
An API is a set of 1 or more programmable functions() that an operating system--or also often an application inside the OS, aka a "program"--exposes to a developer. That's it.
The developer is ordinarily given thousands of API functions() to work with by an OS. Less so, ordinarily, by an individual application. It makes sense because applications are basically processess that make use of OS functions() in order to accomplish something.
A spreadsheet, for example, is just a process that makes a lot of function calls to an operating system in order to display lines and compute characters. It's essentially many calls to the OS API. The collection of API calls just happens to be referred to as a word processor, or an e-mail client, or a web browser, or a paint program, etc.
(Not to be confused with SDK--which is most often nothing more than API documentation (a list of functions and their meanings, usage and sometimes examples).)
An (I)ntegrated (D)evelopment (E)nvironment is an application-building program that incorporates not only a program editor, but also some compiler machinery--even as little as a p-code generator would qualify as such; the IDE would commonly also contain point-and-click keyword-definition help, as well as a library of object definitions, window panes for debug info, etc. The idea is they are all part of one common application-building package, so that you don't have to use a text editor for one step and then have to open up a command line to compile in another, and then use some other program to debug, and on... .
Examples of IDEs include "SharpDevelop," the MS Office "VBE" (VB Editor), "Visual Studio," the "JDE," etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.