permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit f95dc776d214ca2ae769ec06c21c7af4b73cea0b
parent 536967ee484e1ddfebaf74089d59d44c9cb0fb54
Author: viznut_web <viznut_web@web>
Date:   Tue, 14 Jun 2022 22:55:09 +0200

empty web commit

Diffstat:
Mdependency.mdwn | 4+++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/dependency.mdwn b/dependency.mdwn @@ -27,7 +27,9 @@ utilize a program or a device, but this documentation can come from several alternative sources. It can also be omitted if the user has already learned the necessary information. -The compilation dependency of a program on the programming language it is written on is hard if there is only one compiler that can compile the program. However, if there's a large variety of different compilers that all succesfully produce a working executable, the dependency is much softer. The same applies to e.g. websites and how compatible they are with different browsers. If only a few high-end browsers is supported, the dependency is quite hard. +If only one compiler can compile the source code of a program, its compilation dependency is hard. If there's a large variety of different compilers that all succesfully produce a working executable, the dependency is much softer. The same applies to websites and how compatible they are with different browsers. If only a few high-end browsers is supported, the dependency is quite hard. + +Optional dependencies are soft, especially if they don't change the features or behavior of the program. If it is possible to run an application either natively or in a web browser, the monstrous dependencies of the web browser don't need to be taken in account when assessing the application. Permacomputing calls for dependency-awareness, both regarding the material dependencies (the grid, the manufacturing infrastructure, etc.) and the