Discussing the article: "From Basic to Intermediate: Resources"

Check out the new article: From Basic to Intermediate: Resources.

In this article, you'll learn about a concept that can prove extremely useful in many situations and significantly simplify the sharing of your apps and projects. Although it is not easy to fully explain this concept in a single article, what will be presented and explained here will be enough to enable us to accomplish a great deal in the future—including things that would otherwise be impossible. That is exactly why this article has not been published until now: to give you supporting material and a starting point for your studies.

One of the hardest concepts for beginners to grasp is that of so-called resources. I'm referring to resources in terms of code, not hardware. The thing is, the concept of a "resource" doesn't really make much sense when it's introduced into the text just like that, out of the blue. And it makes even less sense when it's explained superficially and hastily, as is usually the case.

To fully understand this topic, you first need to grasp a few concepts discussed in previous articles. So, if you're having trouble understanding a specific point, read the previous articles.

In theory, a resource is a fairly simple concept: a resource is anything you use in a program, as well as anything needed to run the program itself. That is precisely the basic idea. However, as a programmer, you need to have a better understanding of certain details in order to be able to add new elements to an existing program.

First, it should be noted that there are two main types of resources in software. The first type consists of the code's internal resources, and the second consists of its external resources. An internal resource is any element included in an executable file. In contrast, an external resource is something that the program must look for somewhere outside the memory area where the executable file itself is located. It is precisely this distinction that can be difficult to grasp at first. This is because many beginners are quite puzzled when they see that one executable file is capable of performing certain actions, apparently without needing any external files or data, while another requires a large amount of data stored in various locations and in all sorts of external files.


Author: CODE X