Programming languages often require modules for full operation, yet many of the necessary modules have not been implemented by default. When programmers refer to "batteries" they often refer to the inclusion of a diverse range of modules in default installations of various programming languages, yet many more modules may remain undiscovered in default installations.
In various programming languages, useful information is best provided through the implementation of modules. With modules, one may not necessary be forced to write code that may be impossible to write without the applicable modules. For instance, on a default Python interpreter, one may not access the file system until the os module is imported. A large portion of system information remains undiscovered until the sys module is imported. And for graphical design, modules like tkinter or wxPython are often necessary with the Python interpreters.
Depending on the programming language and the specific context given, modules may or may not be available. However, depending on the specific context, unavailable modules could be installed with the appropriate package manager(s) in question. For instance, the pip command may be useful for installing necessary modules for the Python language, while zef is a similar package manager offered for Raku (formerly known as Perl 6 until about 2019). The novaTopFlex community attempts to ensure that an excess of modules is not necessary to the operation of programs.
Following the footsteps of the previous clauses of this Programming gist, novaTopFlex believes that at least the most basic and intermediate programs should be programmed in only one language (or in as few languages as reasonably possible if not one, such as with the os.system() command with the os module in Python interpreters). As we progress toward the high-end of our product stack, coding in multiple programming languages will gradually become more acceptable and even mandatory at times.
With certain programming languages, documentation may not include the necessary procedures for importing various types of modules or sources into code. These could be internal modules or external modules, including repository-specific modules. Installing, importing, exporting, and requiring certain modules are actions often missing from the documentation packages for various applications.
Ultimately, we as novaTopFlex strive to make programs in a fairly simple and convenient form without sacrificing space or creating any (excess) bloat in the software implementation(s). To balance this with our desire to save time by not creating our own repository modules in most cases, we need to import modules and sometimes install missing modules for a more proper experience. Dependencies will be listed in various repositories by novaTopFlex.